From: Alex Khassapov (alex.khassapov_at_[hidden])
Date: 2008-03-27 02:17:01
Vladimir Prus <ghost <at> cs.msu.su> writes:
> Khassapov, Alex wrote:
> > Hi,
> > I wonder if there's a rule I could use to run unit tets which don't
> > require source, i.e. simply execute python scripts?
> No. unit-test assumes that the sources is either EXE, or something
> convertible to EXE. Making unit-test run whatever is passed to it
> will mess up the current behaviour.
> However, to get what you want you can:
> 1. Just use the 'make' rule.
> 2. Use the following:
> import type ;
> import generators ;
> type.register UNIT_TEST_RAW : UNIT_TEST ;
> generators.register-standard testing.unit-test : : UNIT_TEST_RAW ;
> unit-test-raw something : script.py ;
> (This presently assumes that "." directory is in PATH)
> Does this help?
> - Volodya
> Unsubscribe & other changes:
I'll try it.
I was actually thinking of using RUN_OUTPUT type from testing.jam to copy "run"
behavior without compiling, so the output format would be the same - when test
passes we get **passed** message.
I'm just struggling to understand the flow, i.e. how and in which
order â.runâ, â.outputâ and â.testâ files are created?
Any thoughts on this?
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