Document the <start-run> element
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by searching the documentation for existing elements and references to testcasecount or the console runner; no specific file is named in the issue. Done means documenting , noting that testcasecount may be 0 with the console runner, and checking whether the other elements are documented.
Written by the indexing model from the issue text.
Description
I can find no documentation of this element. The key problem here is that the testcasecount may be invalid (value of 0) depending on the runner used. In particular, it's always 0 when running under the console runner. So we at least need to say that somewhere.
At the same time, someone should check into whether we have documetned the other <start-xxx> elements anywhere.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 17h 32m
- Merged PRs (30d)
- 20
Getting set up
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.
More from nunit/docs
-
type:newpage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:framework
Difficulty 4/5 3-5 days Newbie friendliness 40/100
Maintainers usually reply within 1 day
-
Document F# EqualToOpenarea:framework
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
area:framework
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
nunit/docs#1045 · 6 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
agent-reported area/browser area/docs documentation good first issue hacktoberfest help wanted P2
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 2 days