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

Output support (especially with parallel tests) #551

Closed
avonwyss opened this issue Feb 21, 2016 · 2 comments
Closed

Output support (especially with parallel tests) #551

avonwyss opened this issue Feb 21, 2016 · 2 comments

Comments

@avonwyss
Copy link

I'm using SpecFlow 2.0 with xUnit 2.0, and I'm trying to implement code which is able to handle parallel tests properly.

With xUnit 2.0, due to parallelization support, they have dropped support for writing to Trace, Debug and Console; instead the test class should accept a ITestOutputHelper in the constructor and use this for output logging.
https://xunit.github.io/docs/capturing-output.html

Looking at the generated code, the constructor of the class generated by SpecFlow does not capture this as a field. However, I think it would make sense to have a similar concept in SpecFlow (maybe "at home" on the FeatureContext class), and to pass the output through to xUnit using the designed output method.

@samholder
Copy link
Contributor

Please follow #575, this is discussed there

@lock
Copy link

lock bot commented Jul 9, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants