Boost logo

Boost :

Subject: Re: [boost] Test reporting (Was: Process discussions)
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2011-01-31 11:58:34

Rene Rivera wrote:

> On 1/31/2011 10:40 AM, Vladimir Prus wrote:
>> Steven Watanabe wrote:
>>> AMDG
>>> 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
>>>>> results.
>>>>> * 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
>>> understand.
>> Oh -- but are we still using XSLT? Do you think we can
>> easily switch to your C++ translation?
> Yes, as I've mentioned offhandedly recently.. I'm working on a
> replacement for the reporting which is scalable, easy to use, etc.
> Obviously not written in XSLT, but written in Python for Google's App
> Engine Cloud service.

Do you need help?

- Volodya

Vladimir Prus
Mentor Graphics
+7 (812) 677-68-40

Boost list run by bdawes at, gregod at, cpdaniel at, john at