Decide what to do about Incomplete specifications
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
The specifications section of the wiki contains a number of items that were never implemented or were only partially implemented. They need to be reviewed and incorporated in the docs to the extent they were implemented and captured as issues otherwise. Some of them may exist as issues already.
- https://github.com/nunit/docs/wiki/Include-and-Exclude-Attributes-Spec
- https://github.com/nunit/docs/wiki/Extended-Constraint-Syntax-Spec
- https://github.com/nunit/docs/wiki/Dynamic-Test-Cases-Spec
- https://github.com/nunit/docs/wiki/Parameterized-Test-Fixtures-Spec
- https://github.com/nunit/docs/wiki/Test-Dependency-Attribute-Spec
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 reviewing the five linked wiki specifications: Include and Exclude Attributes, Extended Constraint Syntax, Dynamic Test Cases, Parameterized Test Fixtures, and Test Dependency Attribute. Compare each specification with the existing NUnit documentation and issue tracker, checking whether related issues already exist. Done means implemented behavior is documented and unimplemented or partial work is captured in clearly scoped issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100