pytest-dev / pytest-dev/pytest
break up the runtestprotocol and create a sequence of setup/teardown/call actions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
the current usage of setupstate and runtestprotocol creates problematic quirks with tear-down,
to elevate that problem and separate reports better, we should instead have a generator for setup/teardown actions and use those to report setup of items and fixtures as well as the running of items
that way we could remove the need for next-item and ensure each report is much more specific
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 current usage of setupstate and runtestprotocol, with particular attention to teardown behavior and the role of next-item. Define the proposed sequence of setup, teardown, and call actions, then verify that reports distinguish setup of items and fixtures from item execution and that next-item is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100