Fix assertion failure hooks invocation when scenario fail-fast enabled #2095
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.
Fixes #1989
The order of event subscribers invocation for Guava EventBus is not determined,
that fact blocks the ability to put fail-fast mechanism to assertion failure event handler:
if fail-fast event handler doesn't go last, the rest assertion failure event handlers (which
may be adding application source code etc.) will be invoked in improper system state: the
assertion verification is finished, the step is closed in the report.