Internal trace docs incorrectly say the output is sent to the console by default
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Description
https://github.com/nunit/docs/wiki/Internal-Trace#design:
By default, all output through InternalTrace is sent to the console, which means it is mixed with other console output. Note that the trace mechanism bypasses NUnit's redirection of output and displays on the actual Console. Of course, if NUnit is being run without a console - from the Gui, for example - the output will be lost.
But the internal trace is saved to files in the working folder and not shown in the console, and it doesn't look like the user has any control over this.
The entire paragraph should be replaced by one which describes the output .log files, right?
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
Read the Internal Trace wiki page's Design section and verify the current behavior described in the issue: internal trace is saved in working-folder .log files rather than shown on the console. Replace the inaccurate paragraph with wording that matches that behavior, then review the rendered section for accuracy.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100