[qmtest] what is a test database ?

[Stefan Seefeld]

ok, here are two little demo libraries I wrote to learn
more about qmtest.

The first simply scans a tree for '.cc' files and considers
them as tests that need to be compiled and run.

The second is a bit more involved. I wanted to immitate
'conventional' autoconf based build environments, i.e.
suites are directories with makefiles in it. A makefile
now is a python script that is read in and scanned for
build parameters such as CXX, CPPFLAGS etc., as well
as an association between test and test class.

Again, the main goal is for a potential switch to qmtest
to be as smooth and non-intrusive as possible.

I'm not really satisfied with my use of 'Attachments' to
the tests to pass test-specific context data (such as
build variables). Is there a better way ?

Also note that the focus was on 'run', i.e. 'qmtest gui'
will not work.

What do you think about this approach ? Is it reasonable ?
How else could I have solved the problem ?

Regards,
		Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: my_qmtest.tgz
Type: application/x-gzip
Size: 27060 bytes
Desc: not available
URL: <http://sourcerytools.com/pipermail/qmtest/attachments/20030616/7b326d09/attachment.bin>