Theory xml outputs differs based on how you run it
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.6k
- Forks
- 766
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 24
Description
Visual Studio 2019
Running Test Explorer
Looking at the discovery section of the execution dump file from the NUnit3TestAdpter, which is the result from the NUnitEngine/Framework
Running the CSharpDemo project in https://github.com/nunit/nunit3-vs-adapter-demo/blob/master/src/csharp/Theories.cs , the output differs based on how you call the tests.
If you run all tests:
Note that this give you a TestFixture of type Theory
If you however run the tests selected:
They are then reported as Parameterized Tests.
Both works, but shouldn't they be the same, and that is Theory, as in the first
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/csharp/Theories.cs in the nunit3-vs-adapter-demo and reproduce the difference in Visual Studio 2019 Test Explorer by running all tests versus selected tests. Compare the discovery section of the NUnit3TestAdapter execution dump; done means both invocation paths report the theory consistently rather than switching between Theory and Parameterized Tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100