Stop execution of scenario if one step failed/inconclusive (#360)#1198
Merged
nohwnd merged 1 commit intopester:masterfrom Jan 5, 2019
Merged
Stop execution of scenario if one step failed/inconclusive (#360)#1198nohwnd merged 1 commit intopester:masterfrom
nohwnd merged 1 commit intopester:masterfrom
Conversation
- If a step (given/when/then) fails, next steps will be skipped for one scenario - If a step is inconclusive, next steps will also be skipped
Member
|
Fix #360 |
Contributor
Author
|
very fast merge 😮 |
|
@cgnuechtel - is this available now? How do I use it? (I'm just using Invoke-Pester with many, many tests, and I want Pester to stop after the first failure) |
Contributor
Author
|
@nathan-given-health-catalyst my fix was for Gherkin execution, not for PSpec. But I guess for PSpec it was fixed earlier. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As described in #360 it does not make any sense to execute the next steps of a scenario if the current step fails or is inconclusive.
(A step is a Given/When/Then clause.)
(Also with the current pull request Pester should behave more like Cucumber.)