pytest-dev / pytest-dev/pytest
provide a consistent looponfail story based on 3rd party tools
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
looponfail is more than just listening for file changes
also there are more and more tools upcoming that do this more propper and more responsive than what we had in place in xdist
so from my pov we should kill the builtin looponfail and have a well documented and easy to use story for it based on more extensive tools
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 reviewing the existing looponfail behavior in xdist and the third-party tools that provide file-watching test reruns. Define a supported, documented workflow and clarify whether the builtin looponfail should be removed; done means the project has an agreed implementation or migration path and user-facing documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100