nunit-core team mailing list archive
-
nunit-core team
-
Mailing list archive
-
Message #03543
[Bug 1211776] Re: /out command creates a separate blank file
The /out option causes any text output the test sends to stdout to go to
a file. It has nothing to do with the xml results. To change the name
used for the result file, use result:test2results.xml or
xml:test2results.xml.
Your tests probably don't write to Console.Out, so the option is
creating an empty file.
Charlie
** Changed in: nunitv2
Status: New => Invalid
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1211776
Title:
/out command creates a separate blank file
Status in NUnit V2 Test Framework:
Invalid
Bug description:
If I want to rename my 2nd test results, I use the /work:results
/out:test2results.xml. However, I realized this creates the
testresults.xml file with the results data but also, a separate file
called test2results.xml and the contents are blank.
The /out command should only create one file with the tests results
and the new name, right?
I'm using the console runner on NUnit 2.6.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1211776/+subscriptions
References