QMTest running concurrent threads

[Gary Yuan]

Hi,

I have a problem when running QMTest using the -j# concurrent option.
The executable I am testing requires it to be run in a certain
directory away from the QM testdatabase since it needs to open certain
resource and definition files (assuming they reside in the present
working directory). I've implemented a test extension to this effect
using a mechanism like BASH's pusp/pop directory directive. The
problem is that when running when concurrent threads, QMTest doesn't
use a new sandbox environment for each thread but rather picks up
where any current test leaves off. This has the problem of trying to
push a directory from an unintended location, i.e. a directory that
was already pushed. Do you know of any clean solution to this problem?

Thanks.

Gary Yuan.