[Scons-dev] Testing non-core tools

[Dirk Bächle]

Russel,

On 27.07.2013 11:45, Russel Winder wrote:

> On Fri, 2013-07-26 at 21:36 +0200, Dirk Bächle wrote:

> […]

>> If you call the runtest.py for external tests, you have to specify the

>> "-e" option as well.

> OK the -e has helped. Now I am back with:

>

> 1/1 (100.00%) /usr/bin/python -tt test/sconstest-issue_1.py

> scons returned 2

> STDOUT =========================================================================

> scons: Reading SConscript files ...

>

> STDERR =========================================================================

> EnvironmentError: No tool named 'protoc': not a Zip file:

>   [...]

>

>

> So back where I was with the SCons_Testing_Framework. I'll now delete my

> fork of that.

>

> So the question is how to get the test to have the tool available.  The

> SCons_Protobuf project looks like:


I'd say that you now have to apply the basic strategy for detecting 
SCons Tools:

   1.) Either add 'toolpath=["."]' to the environment definition, or
   2.) put the protoc.py in a default path, where it gets picked up 
automatically:

       test.file_fixture('../protoc.py','site_scons/site_tools')    # 
untested!


Does this help?

Best regards,

Dirk


> Sorry to be a pain getting this working. All help gratefully accepted.

That's okay...it's a good start to documenting the remaining quirks and 
warts of the test framework. ;)