Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

When running dotnet test with filter, all tests are run and all console output is logged.

See original GitHub issue

When running a test using the cli(dotnet test) and using a --filter all tests are run but only the results from the filtered tests are reported. A simple repro can be found here. The output from the test run only includes information from the matching test but the non-matching tests also run.

The NUnit version here is 3.13.2 and Adapter version 4.2.0 with dotnet 6.0.101 on an ARM Mac. I can’t be sure it is not an engine issue, but changing the version of the adapter back to 4.1.0 returns to the previous behaviour.

There is another change with this version where the console output is logged for all tests whether they pass or fail. This may well be OS/console specific…

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

OsirisTerjecommented, Jan 21, 2022

Release 4.2.1 is on nuget.org.

1reaction

tmx7777commented, Jan 24, 2022

Works for me as well. Great 👍

Top Results From Across the Web

When running `dotnet test` show output of the `dotnet vstest ...

The command dotnet test -l "console;verbosity=detailed" is showing me all the Console.WriteLine s of my tests just fine. And doesn't clutter ...

dotnet test command - .NET CLI

The dotnet test command builds the solution and runs a test host application for each test project in the solution.

Adapter V4 Release Notes

941 When running dotnet test with filter, all tests are run and all console output is logged. This fix applies to test projects...

Unit Test Runner does not show console output

I run rider on an M1 Mac. Output in Rider (empty): While running it in the CLI confirms there is actually output: dotnet...

How to get output from dotnet test - Terje Sandstrom

A good trick is to add a console logger: dotnet test --logger "console;verbosity=normal" Note: You can configure the adapter through runsettings for different ......