Subject: Re: [Boost-build] Adding command line arguments to tests
From: Christian Auby (christian_at_[hidden])
Date: 2009-11-17 09:09:47
Johan Nilsson wrote:
> How do you capture the test results? IIRC Boost.Test has no built-in
> support for writing XML to file, and you are likely to have xml mixed
> with raw console output if you just tell Boost.Test to generate xml, and
> then run bjam. Can Pulse handle this? Also, can Pulse handle the
> generated Boost.Test XML format? It differs from the JUnit XML format.
It's written automatically to file it seems. See my previous message,
the xml is written to "add.output". It does have a few non-xml things
*** No errors detected
EXIT STATUS: 0
Pulse has a built in boost.test output parser. It only requires XML
though, not sure if I can get it to work without removing the non-xml parts.
> It (bjam) will continue on test errors unless you specify "-q" on the
> command-line. The final status will however be reported as failure if
> any target fails to build. As far as ignoring unit-test target failures
> - what if a test target has a _build_ error (compile/link etc)?
Hmm. If Pulse doesn't pick up tests because of the non-xml data this
might not even be an issue. Will see if I can figure that part out.
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