Steven Weerdenburg

@OsirisTerje The nuget warnings are odd. I've tried to rerun the job. @maettu-this the other failures may just be related to unused using after having removed the attribute. Thank you...

Thanks @manfred-brands Been tough to push changes myself, most of these reviews have been from my phone. I see it building now, will approve and merge after it passes 🙂

I think the idea of allowing more control over this state or scope could be helpful. There's a few other similar discussions over time where some assumptions about pre-3.10 behaviors...

Oh! It was #4461 EDIT: Seems the nature of the issue was slightly different than I remember, but perhaps seeking the same motivation of exposing more control over flow within...

@maettu-this Thanks for the great naming ideas. I admit, I'm on the fence myself about adding this. Exposing a formal API to control NUnit state directly like this takes some...

Thanks @CharliePoole that's a good point and perspective about tests which may "change their minds". My thinking had been that any change here, _if_ made, should still be in the...

I've pushed a repro here confirming the behaviour: https://github.com/nunit/nunit.issues/tree/main/Issue4651 ``` dotnet test --filter "(TestCategory=TestsA&TestCategory!=TestsB)|(TestCategory=TestsC)" ``` A diff of the dump files for both framework `v3.14` and `v4.1.0` yield the same...

I've gotten closer on this one. I think I can commit to getting it done within 4.2

This has been fixed and should release as part of NUnit 4.2

Thanks for this report @DMDTT Can you confirm how you are running your tests (nunit console, the visual studio adapter, resharper, etc) and any relevant version info?