Subject: [boost] Test reporting (Was: Process discussions)
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2011-01-31 11:40:50
Steven Watanabe wrote:
> On 1/31/2011 5:12 AM, Daniel James wrote:
>> On 31 January 2011 10:10, John Maddock<boost.regex_at_[hidden]> wrote:
>>> * The testers machine builds it's own test results pages - ideally these
>>> should go into some form of version control as well so we can roll back and
>>> see what broke when.
>>> * When a tester first starts testing they would add a short meta-description
>>> to a script, and run the script to generate the test results index pages. ie
>>> there would be no need for a separate machine collecting and processing the
>>> * The test script should run much of the above *in parallel* if requested.
>> Is anyone willing to work on something like this? Everyone seems a bit
>> scared of the testing scripts, although I thnk Rene is working on a
>> new reporting system.
> I suspect that this is largely a matter of
> unfamiliarity. I translated most of the
> report generation xsl scripts into C++ last
> year, and I didn't find them that hard to
Oh -- but are we still using XSLT? Do you think we can
easily switch to your C++ translation?
-- Vladimir Prus Mentor Graphics +7 (812) 677-68-40
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk