-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to print live output messages in Test Explorer/dotnet test
output
#408
Comments
Available in Documentation has been updated on enabling this feature:
Using this example test: using Xunit;
using Xunit.Abstractions;
namespace Empty;
public class TestClass(ITestOutputHelper helper)
{
[Fact]
public void TestMethod()
{
helper.WriteLine("This is a line of output");
}
} Output for Output for Test Explorer is in the Output Window, under the Tests tab: |
That was quick, thank you! |
Is there any reason not to always enable this, at least in CI? Does it have a noticable impact on performance, for example? |
There should be no significant performance impact. It's not enabled by default because it's really a debugging tool more than anything else, and live printing output messages makes the output significantly more cluttered (especially with tests running in parallel that are all outputting messages). |
I see, thanks. |
So with this PR,
This is problematic, the test output is now difficult to read. Dropping |
We don't have that level of control. The verbosity from I don't particularly consider "the logs got harder to read" to be a huge problem, since this is intended to be temporarily enabled to help find tests which are running over time and potentially never ending. This is not intended to be permanently enabled. |
@bradwilson Basically I don't want to see logs if with If I want to debug, turning |
Disable diagnostic messages. |
Damn, didn't noticed I had that on... this fixed it thanks. Sorry for this! |
This adds the ability to show output messages in real time, which may assist in debugging a test which is long-running.
The text was updated successfully, but these errors were encountered: