[qmtest] Executable paths and working directories

[Mark Mitchell]

>> Alternatively, you could use the context to tell you where the
>> executables are; that's a perfect application for the context.  (The
>> idea of the context is to provide information about the test environment
>> that might vary over different testsuite invocations.)
>
> Right, that makes sense to me too.  It still seems like there should
> be some more generic way of doing this than defining a special key in
> my context and then having my custom Test class look for it.

Perhaps.

The generic test class can't do it due to the thread issues.

Certainly, we'd like to have a much more extensive set of test classes,
and something along the lines of the command.py classes could definitely
provide this support.

> Oo, good point.  Hmm.  So any generic working directory support should
> probably be implemented in the various command tests themselves, via
> the "dir" argument to Executable.Run.

Exactly.  I see that I just said what you said. :-)

> I think what I'll do for now is add a some sort of "search path" or
> "base directory" attribute to my Test class, and % expand it against
> the context; that seems a nice balance of genericity, flexibility, and
> simplicity, unless anyone can think of a problem with it...

I think that's a solution most consistent with the overall paradigm.

-- 
Mark Mitchell                mark at codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com