© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Comments on the proposed mechanisms...
1. This associates a global option with a particular fixture, which doesn't seem right. It also opens the possibility that more than one TestFixture might specify the location, requiring code in NUnit to either resolve which to use (or randomly pick one) or issue an error message at test load time.
2. This could easily be done in the command-line processing for nunit-console but would make sense in normal gui use, since
the location of saving the file as well as it's name can be specified interactively.
3. I'm not clear on this one. If NUnit is run from a batch file, it's of course possible to run any desired commands after the test run based on the return code. It doesn't seem that reversing the sequence by having NUnit invoke the batch file provides any more flexibility than what's already available.
If we do this, I think #2 is most likely approach. The priority seems low, since it can be done now through a script. On the other hand, it's fairly easy to do.