From: Brad King (brad.king_at_[hidden])
Date: 2002-01-15 22:54:50
I have created another sample implementation of the testing front-end.
The following changes are included:
1.) Split up into module files as in tools/build/new.
2.) Added user configuration of default tester.
3.) General support for introducing new rule types.
It is probably easiest to begin reading the Jamfile, then test.jam, and
then demo.jam. The foobar.jam is an example of how to define new test
types. If you can think of a cleaner way to add test types, please
Some remaining issues were:
1.) Whether to run a test if it is up-to-date.
2.) Up-to-date marker for a test / output file.
3.) Controlling how a run-* test is invoked (ex. for debugger).
I think that these issues should be up to the testing back-end, at least
to some degree. The front-end serves the purpose of collecting test
information and passing it on to the back-ends. It is the job of the
back-end to actually implement the test given a target. Some support from
the front-end may be needed to create both a target for forcing test
execution and a target for updating a test, but I don't know for sure yet.
---1463811583-1093052083-1011153290=:3969 Content-Type: APPLICATION/x-gunzip; name="boostTestFront.tar.gz"
Content-Disposition: attachment; filename="boostTestFront.tar.gz"
[Attachment content not displayed.] ---1463811583-1093052083-1011153290=:3969--
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