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
Even when the "scenario.as.test.fail.terminate" flag is turned on, when executing as a scenario that is marked as a test and one of the building blocks inside fails, the building blocks that follows is still executed even when they were supposed to be skipped.
Steps to reproduce:
Make sure that the "scenario.as.test.fail.terminate" property is turned on.
Create a new scenario s0.
Add a few building blocks that should pass
Add a building block that fails.
Add a few more building blocks that should pass.
Mark the scenario as a test
Create a new scenario s1.
Add scenario s0 to s1
Execute scenario s0.
Result:
All the building blocks in scenario s0 are executed.
Expected result
Building blocks after the one that fails should not be executed.
The text was updated successfully, but these errors were encountered:
It seems that what causes the problem is the XmlReporter. In the startContainer event it resets the run properties which JSystem uses for keeping the property that marks the scenario as test.
Even when the "scenario.as.test.fail.terminate" flag is turned on, when executing as a scenario that is marked as a test and one of the building blocks inside fails, the building blocks that follows is still executed even when they were supposed to be skipped.
Steps to reproduce:
Result:
Expected result
The text was updated successfully, but these errors were encountered: