pytest-dev / pytest-dev/pytest-bdd
--gherkin-terminal-reporter doesn't do expected output for skipped tests
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 251
- Avg merge
- 43m
- Merged PRs (30d)
- 2
Description
See screenshot below. I would expect the steps of the skipped test to be printed out in mustard yellow like the word "SKIPPED".
At a minimum, I would expect the Scenario name to be used rather than the pytest test name.
Using pytest-bdd 3.1.0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the skipped-test output with pytest-bdd 3.1.0 and the --gherkin-terminal-reporter option, using the screenshot and the reported expectations as the reference. Trace the terminal reporter entry point for skipped scenarios; done means skipped steps use the expected mustard-yellow output and the Scenario name is shown instead of the pytest test name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100