Skip to content
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

Closed
bradwilson opened this issue May 3, 2024 · 5 comments

Comments

@bradwilson
Copy link
Member

This adds the ability to show output messages in real time, which may assist in debugging a test which is long-running.

@bradwilson
Copy link
Member Author

Available in 2.8.1-pre.4 https://xunit.net/docs/using-ci-builds

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 dotnet test requires passing --logger console;verbosity=normal to that VSTest does not hide the output from xUnit.net:

image

Output for Test Explorer is in the Output Window, under the Tests tab:

image

@Piedone
Copy link

Piedone commented May 10, 2024

That was quick, thank you!

@Piedone
Copy link

Piedone commented May 10, 2024

Is there any reason not to always enable this, at least in CI? Does it have a noticable impact on performance, for example?

@bradwilson
Copy link
Member Author

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).

@Piedone
Copy link

Piedone commented May 10, 2024

I see, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants