pytest-dev / pytest-dev/pytest-xdist
looponfailroots is not documented
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 287
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 2
Description
The --looponfail option is great for test-driven development but as documented it's somewhat broken if files outside of one's control get modified in the directory pytest is running in since any detected changes trigger a re-run of tests. Luckily it appears that the looponfailroots option can be used to specify which paths to watch, but this feature is not documented in the README.
Contributor guide
No contributing guide indexed for this repository
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 README section that documents the --looponfail option. Document how looponfailroots limits the paths watched for changes, and consider the reported problem of unrelated files triggering reruns; done means the README clearly explains this option and its usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100