Review testing documentation
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 79
- Forks
- 52
- Avg merge
- 18h 58m
- Merged PRs (30d)
- 4
Description
## Summary
Review testing documentation to make it more useful for consumers, in all popular testing frameworks.
## 💬 Description
This spike should include exploring what teams actually want documentation wise for all popular testing frameworks and then either implementing changes or introducing follow up issues that address the issue.
## 💰 Use value
Make it easy for consumers to test components with any library.
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
No documentation files or testing frameworks are named. Start by locating the testing documentation, then research what consumers need across popular frameworks. Done means either making the agreed documentation improvements or creating follow-up issues that clearly capture remaining work.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100