From: Steven Knight (knight_at_[hidden])
Date: 2002-03-26 10:09:37
One comment I forgot...
> I had a hard time getting excited about QMTest, personally. IIRC, it
> struck me as a very generic test execution and results-gathering and
> reporting framework. That's fine so far as it goes, but it solves the
> easy part of the problem. It still leaves you to create all of the
> actual infrastructure for your testing environment, the stuff that
> determines whether it's difficult or easy for Joe Developer to actually
> *write* a test.
Because QMTest is so generic, the TestCmd.py module I described should
work just fine within a QMTest framework for test execution. You
should be able to use TestCmd.py as underlying infrastructure for how
the individual tests are written, and QMTest for executing tests and
collecting and displaying the results.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk