Reimagine waived tests in terms of "known issues"
Open
- Dominant language
- Python
- Stars
- 2
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
"Waived" tests as we have them right now is just a case of a "known issue", support for which we're planning to implement.
See if we can replace the "waived" flag completely with the "known issues" system.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the current `waived` flag and the planned known-issues support, then determine how their data and behavior overlap. Done means the separate waived flag is removed and the existing waived-test behavior is represented by the known-issues system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100