Steven Weerdenburg

I'm going to close this due to inactivity, but @Daedra22 please let us know if mikkelbu's answer didn't help, and any additional context you could provide which could further help...

@manfred-brands Just doing a bit of cleanup here. Should this be closed as superseded by https://github.com/nunit/nunit/pull/4386 based on your comment in https://github.com/nunit/nunit/issues/4447#issuecomment-1661516745 ?

Thanks for raising this @lucasteles , as well as for already getting the fscheck perspective by asking there too. While this issue tracker is a good place for framework-related or...

Hi @MichalMucek Unfortunately there are a few issues with the 3.16 version of the console runner. Since you have .NET8 installed could you please see if the prerelease of 3.17...

@Paciv I haven't personally been able to check this out yet, but there may be a typo in your command (`NUni.Where` vs `NUnit.Where`). Assuming that `AssemblyInitialize` also contains tests, have...

Thanks @Paciv Without digging deeper, I'm wondering if you're hitting this behaviour (from https://docs.nunit.org/articles/nunit/writing-tests/attributes/setupfixture.html): > A SetUpFixture outside of any namespace provides SetUp and TearDown for the entire assembly. While...

Can you help me understand a bit more about why you need to target this setup class specifically? Based on how you've described it, with no namespace and decorated with...

I'm beginning to wonder if you're perhaps looking for the process-wide "global setup / teardown" functionality described in https://github.com/nunit/nunit/issues/4106

Thanks for reporting this @jochenwezel I haven't had the chance to dig into this myself yet but there may be two separate issues here. For your first point, I'm reminded...

Also, thank you for the clean repro and package version info. Can you also please confirm which version of Visual Studio you're using?