CATcher-org / CATcher-org/CATcher
Tester response phase: Update faulty issues text
- Dominant language
- TypeScript
- Stars
- 92
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
Current:
Problem: This can also appear for issues not selected to be sent to dev response phase i.e., the tester left more than 6 bugs open, and this bug was not among the ones PE script auto-selected.
Suggested:
> No valid developer/tester response was found. It is likely this bug was not selected to be sent to the 'Developer response' phase. If that is not the case, please contact the teaching team for assistance.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in the tester response phase by locating the current faulty-issue message shown in the issue screenshot. Check how issues not selected for the Developer response phase reach this message, then update the wording to distinguish that case and verify the suggested text appears when no valid developer/tester response is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100