--noresult flag results in TestResult.xml file being written with test results #1748
Description
As the title summarizes: I wanted to run nunit3-console without creating the result file (for testing an issue with the test that is sometimes failing, probably due to the load on the system). I've discovered the --noresult option but upon testing I see that it is still writing test results to TestResult.xml.
Is this correct behavior or bug? Or is there other way to get "quiet" test run?
- The full command line being used:
nunit3-console --test ClassName.AndTestMethodName --inprocess --noresult .\UnitTests.dll - Method of installation: chocolatey
- Version of the NUnit Engine/Console: Nunit3 console: 3.20.1
I can see in the code that specifying --noresult sets property NoResult on ConsoleOptions class to true which later is checked before running the tests but the result of tests is always passed to all objects in ConsoleOptions.ResultOutputSpecifications list.