Should the process include something about Testing?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 262
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
The process gives guidance on "implementation experience" as being necessary for the process, but not for Testing. Our discussions in the Working Group Effectiveness task force have made me consider that maybe testing is almost as important as implementations for specs. Should we therefore include something about testing in the process doc?
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
Start by reading the process document's guidance on implementation experience and the related discussions from the Working Group Effectiveness task force. Determine whether testing should be represented in the process and what concrete wording or scope the document would need; completion requires an agreed process-document change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100