Re: [Boost-build] [qt4] patches and testcase

From: Jurko Gospodnetiæ (jurko.gospodnetic_at_[hidden])
Date: 2008-07-04 06:00:11

   Hi Juergen.

>>> Does anyone have an idea _where_ to put it ?
>>> Please consider that you have Qt4 installed and setup in
>>> user-config.jam in order to run the tests...
>>    That seems like something to into the Boost Build test suite. That
>> one is located under the tools/build/v2/test folder.
> 
>>    The tests there are written in Python. There is a some tester
>> class there with some built-in functionality to ease your testing
>> like making running Boost Build in a temporary folder, creating input
>> files, checking which files for removed/created/modified by the build
>> etc.
> 
> Well, those are _low_ level tests for basic functionality.
> My Qt test case tests "end-user" functionality. They can even be used as 
> examples on how to use qt4.jam. And for testing if the end users has a 
> working "user-config.jam" with correct Qt4 settings.

   I'm not really sure what 'end-user functionality' is supposed to mean 
here or what is 'low level' about those Boost Build tests. They can 
contain any kind of build script, may use or expect any sort of 
configuration available on the system running the tests, may run the 
build and may analyze the build results... Not sure what more you need.

   You have an external runner (Python testing scripts) and the program 
to test (Boost Build). I'd categorize existing Boost Jam tests and 
testing framework as 'low level' as they do not have an external runner 
but I really do not know what more could be done for Boost Build tests.

   Obviously more testing & utility functions could be added but nothing 
in the test framework design prevents this. Also, possibly a bridge 
could be made between Boost Build towards its testing system so that 
those tests could be run from a Boost Build script and so get integrated 
into regular Boost library tests but again - I do not think anything in 
the test system design prevents this.

> But I'd rather do the testing on "end-user" level.

   Again... not sure what 'end-user level' means here.

   Best regards,
     Jurko Gospodnetiæ