-
For some time we are getting this error when doing tests
`NUnit report watcher
12:50:33 No reports found for paths:
12:50:33 /Users/xxxxxxxxx/Downloads/TeamCity/buildAgent/temp/agentTmp/uni…
-
I have an NUnit test project with a dependency on `coverlet.collector v3.0.3` which becomes unusable when `dotnet test` is invoked with `--collect:"XPlat Code Coverage"`.
Repro steps:
```bash
git…
-
**Describe the bug**
It's currently possible to group all tests 'By Duration', so that the user get some insights about slow running tests. That's already fine!
It would be even more helpful for the …
-
Because the dotnet tool is a standalone executable, extensions are difficult to locate because they are installed about eight directory levels above the runner and engine. This requires a more agressi…
-
Since version 7.7 I no longer can see the list of tests in the testing area of VSCode.
Reverting to 7.6 does not seem to have this issue. I also tried different ways of setting the project path in se…
-
## Description
There are times when we want to capture multiple assertions at the same time. For example, checking a set of properties for equality.
Assert.AreEqual(key, echo.EmployeeClassifica…
-
Environment:
Runner: VS Test Adapter v4.5.0
Target Framework: .net8.0
There seems to be a difference in how NUnit 3.14 behaves compared to NUnit 4.1 regarding the exception `System.Reflection.Tar…
-
This will require either separate installation of the V2 driver extension or bundling it with the NUnit 3 adapter. I'd prefer to keep them separate but its a little uncertain how the extension will be…
-
Currently there is only one way how user is able to say where `nunit-console` should find extensions. This is via `*.addins` file. What if user will be able to install extension via nuget into tests p…
-
```
What steps will reproduce the problem?
1. Open a solution containing NUnit tests
2. Hit Ctrl+R, A to run all the unit tests in the solution
3. View Test Output and note the NullReferenceExcepti…