never tried it, but is there any reason that you can't just use the XMLDoc
documentation? Since NUnit tests are simply methods of a test fixture,
would this suffice for what you need?
Are you using NUnit tests for a formalized testing process? That's unusual.
(not right or wrong... I just haven't seen it done). The reason is that
unit tests are usually done by developers to (a) drive the development to a
good stopping point (TDD), and (b) insure that they know when a change to
functionality has broken something... they are not normally used for code
coverage, functional testing, or integration testing, where test plans are
more often used.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
<ge*****************@yahoo.co.uk> wrote in message
news:11**********************@l41g2000cwc.googlegr oups.com...
By the way I've seen NUnit2Report and NUnitReport - nice tools but
these are for documenting the test results - I need something that
documents the tests.
For example, rather than:
myClassTest.Connection - Passed.
I need
myClassTest
Tests done on the class responsible for blah, blah,
Connection
Check that the class can connect sucessfully.