[TASK] Implement a review process to verify new tests
Open
Nobody has claimed this yet.
kind/plan-task
- Dominant language
- No language data
- Stars
- 84
- Forks
- 149
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 29
Description
Description
New tests and components should follow the established best practices.
Acceptance Criteria
- Include some automated verification
- Process is in place to catch violations during code review
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
The issue names no files, tests, or entry points; start by locating the repository's established best-practice guidance and current review or automated-check configuration. Done means an agreed process is documented and an automated verification step is in place to catch violations during code review.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100