--explore - output to stdout/allow format option to be specified without specifying output file
Open
Nobody has claimed this yet.
Enhancement
V4Plus
- Dominant language
- C#
- Stars
- 234
- Forks
- 163
- Avg merge
- 13h 32m
- Merged PRs (30d)
- 25
Description
Currently the --explore option with no arguments will list the tests available in the assembly in a flat text list:
>nunit3-console SomeTests.dll --explore
NUnit Console Runner 3.5.0
Copyright (C) 2016 Charlie Poole
Runtime Environment
OS Version: Microsoft Windows NT 10.0.10586.0
CLR Version: 4.0.30319.42000
Test Files
SomeTests.dll
SomeTests.Class1.Test1
I want this list in the NUnit3 xml format, but when I try this
nunit3-console MHR.Test.Recruitment.Features.dll --explore;format=nunit3
An exception message is displayed.
I would prefer not to have to dump the results to a file to read them. Is there anyway I can get XML output from stdout using --explore?
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 console runner's --explore handling and command-line parsing for the format and output options. Reproduce the shown command, then verify that NUnit3 XML can be written to stdout without requiring an output file and that the exception no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100