When AllureFormatter.hide_excluded=True, Behave still reports step declarations for tag-excluded scenarios to the formatter. The listener dropped those scenarios without clearing its pending step queue, so their steps were later attached to the next included scenario.
This change clears pending steps when a scenario is dropped and adds an acceptance test that verifies a selected scenario contains only its own step.
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
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.
Context
When AllureFormatter.hide_excluded=True, Behave still reports step declarations for tag-excluded scenarios to the formatter. The listener dropped those scenarios without clearing its pending step queue, so their steps were later attached to the next included scenario.
This change clears pending steps when a scenario is dropped and adds an acceptance test that verifies a selected scenario contains only its own step.
Fixes #902
Checklist
Verification