Closed yoyos06 closed 8 years ago
@NedNedyalkov what versions did you upgrade from?
@mikkelbu I narrowed it down to NUnit3TestAdapter being the culprit. I've confirmed that my old version 4.0.0 works as I expected and 4.5.0 does not.
This has been discussed and changed over time, also as a result in the dotnet test handling of console outputs.
The most relevant now is this one: https://github.com/nunit/nunit3-vs-adapter/issues/1102
And there is an open bug in the adapter for stopping console output completely, due in 4.6 https://github.com/nunit/nunit3-vs-adapter/issues/1109
I would assume this belongs in the same group.
The defaults have changed over time, there are multiple settings for this, and it is currently hard to get a good grip on it.
We do however need to collect and document all the different settings and their effects.
Some links: Info on ConsoleOut Info on Trace and Debug Info on Progress messages Info on Test Explorer warnings Discussion on default settings, what it should be
The Nunit 2 console had a great feature, it reported the test output on the fly and not only after the test finished. It was very useful because you could track the test case and check the progress, but now I have to wait the end of the test case to see the output. Do you plan to reimplement this feature?