"W. Martin Borgert" <[email protected]> writes: > Quoting "Johnny Chang" <[email protected]>: >> I looked at the documentation and it wasn't clear to me how to run a >> test suite, look for output, and check in. Can you give me some >> hints? > > Running tests itself is not in the scope of bitten (and would be > the wrong place IMHO). You run e.g. unittests (in my case junit > tests via ant) and bitten makes the logs available via trac. For > further questions I suggest you ask on the bitten mailing list.
Seconded, all of it. From what I've looked at (haven't tried anything yet in this area), several of the *unit elements can parse the test results and put this up on the build page. There is also support for test coverage and test success/failure ratio graphs. Have a look at http://bitten.edgewall.org/build/trunk/1456#step_test http://bitten.edgewall.org/build/trunk to get an idea. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
