-
Notifications
You must be signed in to change notification settings - Fork 44
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
Issue with configuration file reqnroll.json #268
Comments
I cannot reproduce the problem. I have used a simple calculator demo app with the following scenario (both Then steps fail):
Without any config, it "continues", so I see the test log as
But if I add a config file as
Then the output changes to (note the missing second Then step):
Could you please double check:
|
Hi @gasparnagy, I've recreated the specflow project and now all is working fine (I don't know why, because I already tried to rebuild the project previously and the config file was already in root folder). Anyway now it's working... |
@d4v1dk0n7 no prob. Closing the ticket. |
Reqnroll Version
2.1.0
Which test runner are you using?
NUnit
Test Runner Version Number
4.2.2
.NET Implementation
.NET 8.0
Test Execution Method
Visual Studio Test Explorer
Content of reqnroll.json configuration file
{
"$schema": "https://schemas.reqnroll.net/reqnroll-config-latest.json",
"language": {
"feature": "en-US",
"binding": "en-US"
},
"generator": {
"allowDebugGeneratedFiles": false,
"allowRowTests": true,
"addNonParallelizableMarkerForTags": [ "nonparallelizable" ]
},
"runtime": {
"missingOrPendingStepsOutcome": "Pending",
"obsoleteBehavior": "Warn",
"stopAtFirstError": true
},
"trace": {
"stepDefinitionSkeletonStyle": "CucumberExpressionAttribute",
"coloredOutput": true
},
"bindingAssemblies": [
{
"assembly": "QA.TestCore"
}
]
}
Issue Description
Hi team,
First of all I would like to thank you for the incredible work you're doing!! Reqnroll is a fantastic tool :)
I've noticed that the setting "stopAtFirstError" is not working as expected, when I execute the tests and some step fails it continues with next step anyway, even if you have configured the "stopAtFirstError" setting as "true".
As far as I understand with this setting activated once one step fails it shouldn't execute the next... Or I'm missunderstanding how this works?
If I'm wrong please feel free to close the ticket.
Thanks!
Steps to Reproduce
Just executing the tests you'll see that aren't stopping in the first error.
Link to Repro Project
No response
The text was updated successfully, but these errors were encountered: