The logger thing is definitely something we've talked about before, but no
one has been brave enough to sit down and do it.
One of the things we've talked about, is writing the test results out in a
certain file, so that a listener program on the host computer can determine
which tests succeed or fail, and generate perhaps an NUnit style report on
it.
Ideally, we'd like to continue pumping tests into the kernel, which can be
optionally compiled to be enabled, and then get comprehensive reporting on
what works, and what doesn't - and do it *all* in an automated build /
continuous integration process.
But, like I said, none of us have the time for that really, and what we are
doing, works for now. So any work you do in that area would *definitely* be
appreciated...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
