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
SpecFlow Section in app.config or content of specflow.json
No response
Issue Description
Consider the following code.
[AfterStep]publicstaticasync Task TearDown(){
#pragma warning disable CS0618 // Type or member is obsoleteif(ScenarioContext.Current.TestError !=null){
Console.WriteLine("Failed");}
#pragma warning restore CS0618 // Type or member is obsolete}}
I am trying to trigger a function as a test has failed.
I can reach the console log succesfully when a test fails, however I am presented with a warning that refers to a piece of documentation - that documentation does not exist when I search for it.
Steps to Reproduce
See description.
Using ScenarioContext.Current gives a warning despite working as intended.
Link to Repro Project
No response
The text was updated successfully, but these errors were encountered:
With SpecFlow 3.0, we marked ScenarioContext.Current obsolete, to make clear that you that you should avoid using these properties in future. The reason for moving away from these properties is that they do not work when running scenarios in parallel.
SpecFlow Version
3.9.74
Which test runner are you using?
NUnit
Test Runner Version Number
3.13.3
.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
No response
Issue Description
Consider the following code.
I am trying to trigger a function as a test has failed.
I can reach the console log succesfully when a test fails, however I am presented with a warning that refers to a piece of documentation - that documentation does not exist when I search for it.
Steps to Reproduce
See description.
Using
ScenarioContext.Current
gives a warning despite working as intended.Link to Repro Project
No response
The text was updated successfully, but these errors were encountered: