Docs for running tests under the console no longer work
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the installation documentation at https://docs.nunit.org/articles/nunit/getting-started/installation.html and verify how the NuGet console runner is installed and used in the .NET Core environment. Done means the instructions no longer assume installation in a packages folder and accurately describe a working console-runner workflow.
Written by the indexing model from the issue text.
Description
This applies to the nuget package. The documentation at https://docs.nunit.org/articles/nunit/getting-started/installation.html assumes that the package will be installed in the packages folder. This is no longer true.
I'm filing this for somebody else to take on, since I'm not very clear myself as to how a nuget install of a tool like the console runner ought to be used. In fact, I'm wondering if nuget is the right choice for a tool these days, but that's a different matter. If someone has a clear idea about how to use a nuget install of an executable tool in the net core environment, please take this on!
- Dominant language
- Dockerfile
- Stars
- 601
- Forks
- 158
- Avg merge
- 15h 46m
- Merged PRs (30d)
- 23
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
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 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
kernc/backtesting.py#1413 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100