Docs for running tests under the console no longer work
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
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!
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 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.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100