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

TestContext.Progress output. #621

Closed
vpenades opened this issue Mar 26, 2019 · 4 comments
Closed

TestContext.Progress output. #621

vpenades opened this issue Mar 26, 2019 · 4 comments

Comments

@vpenades
Copy link

In my tests I am using TestContext.WriteLine for writing test outcome to the output panel, and TestContext.Progress.WriteLine for writing test progress to the console, so I can see the progress for very heavy tests.

The problem is that TestContext.Progress is also writing to the default output, so in the output panel, I have test data and test progress mixed.

Is there a way to prevent Progress to write to the output window, and let it write only to the console?

I think Out and Progress are expected to be used for different purposes. I consider "Out" to be a place to write test outcomes, while Progress is meant to allow monitoring the running process, and both outputs should not be mixed.

@CharliePoole
Copy link
Contributor

The theory behind Progress output is that each runner will decide how to display it.

For example, the console runner displays it immediately to the console without any buffering. A hypothetical GUI might have a dedicated panel for it. It's up to the designers of each runner.

So this really seems to be an issue for whatever runner you are using rather than for the framework. If it's the NUnit 3 VS adapter, we can transfer it there for you.

@vpenades
Copy link
Author

@CharliePoole Hi, yes, it is the VS Adapter.... sorry for posting the issue here (again) ... I use NUnit, but I don't know much about what's under the hood, so I am never sure when it's NUnit or the Adapter responsability.

@CharliePoole
Copy link
Contributor

I'll transfer it when I get to my computer. Can't do it on the phone.

@OsirisTerje
Copy link
Member

@vpenades Included in version 3.14, released today, Aug 8th 2019

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

3 participants