Display scenario tags in gherkin terminal reporter - #830
Closed
ryux1 wants to merge 1 commit into
Closed
Conversation
Author
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
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.
Closes #476.
Scenario tags are already serialized into the report context, but the Gherkin terminal reporter never renders them. This adds a small shared writer and emits
(tags: ...)after the scenario result in both verbose modes. Untagged scenario output remains unchanged.Validation:
pytest -q: 144 passed, 1 skippedThe repository-wide Ruff run still reports the pre-existing
ISC004finding intests/generation/test_generate_missing.py:80; this PR does not touch that file.