Understand and fix hypothesis issues
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
We need to invest some time and effort into understanding and fixing the increasing number of problems that we are seeing in our hypothesis tests.
EDIT THIS COMMENT TO PROVIDE MORE DETAILS AND LINKS TO RELEVANT PRs etc. ... when I have some time ..
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 repository's hypothesis tests and collecting the problems referenced by this issue. No files, failing tests, or concrete symptoms are named, so the first step is to identify the affected tests and relevant history. Done would require understanding the reported issues and fixing them, with passing hypothesis tests as evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100