You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
andConsole
; instead the test class should accept aITestOutputHelper
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.The text was updated successfully, but these errors were encountered: