[qmtest] writing composite tests

[Stefan Seefeld]

Mark Mitchell wrote:

> We've actually got some pretty nice test/database classes for
> compiling/linking/executing programs.  We should probably get those into
> QMTest proper, but we've never had the time to check over the interfaces
> as much as we'd like, and I'd like to avoid changing them after they go
> into QMTest.
> 
> You can get them out of the "qtmc" module in the same repository as
> QMTest.

ok, thanks, will do.

[...]

> We've intentionally made it hard for one Test to get its hands on
> another Test.  The reason is that tests should be independent of
> another; this is another design goal.  If tests are not independent of
> one another then running one test is no longer a well-defined operation;
> each test is potentially dependent upon context created by other tests.

Ok, understood. I should have been clearer: I didn't mean to suggest any
dependency relationship between tests, but only between test *classes*,
so I can use the 'composite' design pattern. From a user's perspective
there would only be a single test, and the result would contain all the
relevant information about passes or failures.

Regards,
		Stefan