Open renycorreia opened 1 year ago
I've been seeing the same issue. It would be nice to get this fixed so that we can have Inconclusive rather than failed.
Same, it would be nice if the inhouse test ignore did not show as a fail on the report
This is a major issue for anyone with >10 tests in various feature files that they must dynamically ignore.
SpecFlow Version
3.9.74
Which test runner are you using?
xUnit
Test Runner Version Number
3.9.74
.NET Implementation
.NET 6.0
Project Format of the SpecFlow project
Sdk-style project format
.feature.cs files are generated using
SpecFlow.Tools.MsBuild.Generation NuGet package
Test Execution Method
Visual Studio Test Explorer
SpecFlow Section in app.config or content of specflow.json
Issue Description
.NET Implementation
.NET 7.0 right now, but I had the same issue using .NET 6.0
SpecFlow+ LivingDoc Version
3.9.57
I've configured some tests to be ignored, based a few conditions, using _unitTestRuntimeProvider.TestIgnore("some message") in one of the steps. It works fine, except that the step and the scenario were set as failed.
I was able to change the scenario state to Skipped using the code below at the AfterScenario hook.
However, the step is taken as as failed, as can be seen in the json snippet below .
This causes the Analytics tab of the Livingdoc report to indicate that there is a failed step. Even though there is no failed scenario or feature.
Is there a way of doing this without indicating that the step is failed?
Steps to Reproduce
Link to Repro Project
No response