NUnitLite currently lives in two places.
1) The NUnitLite project, which has been released as 0.6.
2) The NUnit 3.0 project, which has released version 2.9.5 of nunitlite.
Currently, I'm working to bring the NUnitLite project into conformance with
the code that's now under NUnit. I'm hoping to reach a point where I
can release version 1.0 and then move all development over to NUnit,
where the first production release will be numbered 3.0.
Neither version of the code currently produces an XML file of results, but
the NUnit 3.0 code would be much easier to modify to produce such a
file, since it's TestResult type knows how to represent itself as XML, while
that in the NUnitLite project doesn't yet have that abilitiy.
This is a desirable feature and I'd be glad to work with you to get it
done and incorporate the result in the release. To get started, you'll
need to branch the entire nunit-3.0 project using bazaar. However, you
would only be working in the NUnitFramework solution, since that's
where nunitlite lives. The code that needs to be modified is in TextUI.cs
and most likely also CommandLineOptions.cs.
Feel free to contact me for any help with the details.
Charlie
> --
> You received this message because you are subscribed to the Google Groups "NUnitLite" group.
> To post to this group, send email to nuni...@googlegroups.com.
> To unsubscribe from this group, send email to nunitlite+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/nunitlite?hl=en.
>
So... I started looking at the NUnitLite 3.0 code and before I knew it
I had implemented
the saving of the result file. If you get the latest code, it's included.
With NUnitLite, the result is not saved by default, so you have to use
the option
-result=filename if you want it. Note that the result is saved in the
NUnit 3.0 format,
rather than NUnit 2.x.
Charlie