Add explanation for what TestOf really does
Open
Nobody has claimed this yet.
pri:p3
type:update
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
In the documentation for TestOf, it isn't explained what it actually does. Is it just a strongly typed way of stating, for human readers, the class that is tested? Or does it have more functional uses?
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 with the TestOf Attribute documentation page linked in the issue and review the surrounding NUnit documentation. Determine whether TestOf has functional behavior beyond identifying the tested class, then update the page so its purpose and behavior are clear to readers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100