Create testing plan
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Issue https://github.com/w3c/wot-scripting-api/issues/117 is a bit too specific. What is needed is a plan outlining how a scripting API implementation is tested for conformance with the specification. This can be a simple .md file, and may or may not use the assertion extraction mechanism used for the TD spec. Also the definition of "feature" should be discussed; features are points of the implementation to be tested but may or may not map directly onto assertions in the text. They may also relate to (for example) each entry point in the API defined in the IDL.
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 issue 117 and the specification's scripting API entry points defined in the IDL. Draft the requested .md testing plan, considering whether to use the TD specification's assertion-extraction mechanism and how to define features. Done means the plan explains how an implementation is tested for conformance and how features relate to assertions or API entry points.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100