From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-05-05 15:04:09
> One thing though... For bjam I would really like it if tests got added
> to the jam/test also.
I can write the NORMALIZE_PATH tests easily enough there since they
do not require any external files, but these short/long filename tests
do require external files and though I know how I could implement the
tests here (by creating temporary files in one bjam run which then calls
itself again to do the actual handling and remove the source files in
the end...) the tests as prepared in the Boost Build test suite seem
much cleaner (including - having less test code duplication and/or much
more separated tests).
Anyone against merging the testing infrastructure/plumbing used for
both Boost Jam & Boost Build testing? Those Python classes currently
prepared for Boost Build make it much easier to prepare tests.
I could make it happen, including making the existing Boost.Jam tests
run in the new system, but I'd need advice on where to place this shared
testing framework? If it is used by both Boost Jam & Boost Build then it
does not seem to belong under the Boost Build folder...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk