The Test Result file isn't intended to be human-readable, except when used for debugging. It's a source for all the data about a test run from which human-readable reports may be generated.
There are two ways to generate a report
- As a part of the test run itself.
- After the run is finished, using the test result xml file.
Reports generated as part of the test run require a report writing extension. You would write such an extension following the documentation to produce the report in whatever format you require, like text or html, and give it a unique tag likemyreport
.
You would install your extension and could then run the console runner including an option like
--result:somefile.html;format=myreport
As you may guess, creating your own extension is a relatively advanced use of NUnit.
Another option, if you are familiar with XSLT processing, is to use the built-in report format user
, together with an XSLT transform. In that case, the option is something like
--result:somefile.html;transform=mytransform.xslt
You can also produce a report after the run is finished using the XML output file. The NUnit console program is not used in this case. You must use some standard program for creating reports from NUnit output (or a generic program taking XSLT transforms) or write your own program.