test: prove every scenario can fail (mutation meta-test)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 1
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 63
Description
#606 is a test whose only assertion is satisfied before credentials are submitted — it can never fail, and nothing detected that. docs/test-architecture.md already warns about "a check that can never fail"; this makes the warning enforceable.
Run the suite against a deliberately broken deployment fixture (wrong password, product stopped, unreachable URL) and assert the relevant scenarios go red. Any scenario that stays green under mutation is not a check. Start with authentication and reachability, where a vacuous pass is most damaging.
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 with test #606 and read docs/test-architecture.md, especially the warning about checks that can never fail. Run the suite against the stated broken deployment conditions—wrong password, stopped product, and unreachable URL—and identify the authentication and reachability scenarios. Done means each relevant scenario goes red under its corresponding mutation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100