"Not a TestFixture, but TestSuite" error when using un-namespaced SetupFixture
See original GitHub issueNote: only occurs using the 4.0.0-alpha.1 release. 3.17 appears fine.
When using a SetupFixture outside of a namespace, the new DiscoveryConverter doesn’t handle the case where a test suite appears inside of the setupfixture node when reading tests from the assembly.
- NUnit and NUnit3TestAdapter versions: NUnit - 3.12.0, NUnit3TestAdapter - 4.0.0-alpha.1
- Repro: https://github.com/nunit/nunit3-vs-adapter.issues/pull/2
- Repro steps:
dotnet test TestLib.sln
- .net framework or core.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
NUnit - Fails with TestFixtureSetUp method not allowed on ...
I'm using 2.6.2 version and the text is "TestFixtureSetUp method not allowed on a SetUpFixture". However I have answered my own question by ......
Read more >SetUpFixture
SetUpFixture. This is the attribute that marks a class that contains the one-time setup or teardown methods for all the test fixtures in...
Read more >Lifecycle of a test fixture
NUnit supports multiple SetUpFixture classes: in this case, setup methods will be executed starting from the most external namespace in and the teardown...
Read more >Bugs with Parameterized Test Fixtures
I have made a parameterized test fixture in play mode which exactly the same with the demo code in nunit official documentation:TestFixture ......
Read more >NUnit tests not run due to an exception in SetUp on a ...
I just tested it with NUnit 2.5.3 and it reported all of the test methods as Failed with a message of "Parent SetUp...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It happens even if the SetupFixture is inside a namespace. Which is a bummer, as I badly need the new Explicit handling from this package.
had the same issue as @VoidPtr74 and the mentioned package by @OsirisTerje solved it, so even if I am not OP, I can confirm the solution is working! 👍 Thanks for your greak work!