Andrew Savige wrote: > We are looking at introducing continuous builds/smoke tests at > work across a number of platforms (mainly Windows and Unix), > building a number of different languages (mainly C++). > > I quick google uncovered the list below. > > Anyone got any advice?
I would advise keeping the test-harness and the test reporting separate. In Perl, we like the TAP (Test Anything Protocol - http://search.cpan.org/~petdance/Test-Harness-2.60/lib/Test/Harness/TAP.pod) for test output. And there are implementations in various other languages. Since you're using C++, you can probably use libtap (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the tests and then you could use a Perl harnes to collect those results. In a shameless plug, you might look at smolder (http://sourceforge.net/projects/smolder) as your reporting tool for the tests. It's currently in beta, but will probably have a 1.0 release in the next few months. It acts as a standalone server that recieves TAP based smoke reports from tests (either uploaded by developers or uploaded by automatic runs) and then provides some basic reports. It can even email developers when a test fails unexpectedly. -- Michael Peters Developer Plus Three, LP
