Invoke After Scenario hooks after After Step hooks #444
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.
Description
This PR refactors hooks handling to improve invocation order.
This is not exactly a perfect solution for the problem, but an improvement.
After Scenario will be invoked after step hooks of the last step in scenario or after a first failing step in scenario (all consecutive steps would have skipped status).
After Scenario will be invoked before skipped steps even though these steps are wrapped with step hooks.
Maybe it makes sense to disable step hooks for such steps for better consistency, but that may turn out a disruptive change of behavior.
Motivation & context
Fixes #434
Type of change
Note to other contributors
No note.
Update required of cucumber.io/docs
No update.
Checklist: