pytest-dev / pytest-dev/pytest-bdd
Identifying scenario failure and step that caused failure in after scenario hook
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 251
- Avg merge
- 43m
- Merged PRs (30d)
- 2
Description
I saw the conversation marked in #143 regarding accessing the test state of a scenario after execution in an after_scenario hook but still feel like this is something that should be properly supported?
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 reading the discussion in #143 and the current after_scenario hook behavior. Clarify how scenario test state, the failure, and the failing step should be exposed after execution; done means the agreed behavior is covered for a failing scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100