W3C home > Mailing lists > Public > public-test-infra@w3.org > July to September 2011

Re: Automatic test results reporting

From: Francois Daoust <fd@w3.org>
Date: Wed, 10 Aug 2011 18:52:53 +0200
Message-ID: <4E42B765.2020902@w3.org>
To: Bryan Sullivan <blsaws@gmail.com>
CC: Philippe Le Hegaret <plh@w3.org>, public-test-infra <public-test-infra@w3.org>
See email I just sent in reply to James message.

Instead of an API, it might be easier, once we have a "result of the session" page that lists the results about to be submitted, to provide an "export" button that would give the user a copy of the results in some format (CSV, JSON, XML, etc.).

Francois.

On 08/10/2011 03:19 PM, Bryan Sullivan wrote:
> Hi Francois,
>
> A useful feature would be to allow a tester to define the test results
> collection server address, and for W3C to publish the API that the client
> side of the framework will use to deliver the results. This will allow
> testers to do preliminary testing, and automatically collect the results at
> their own server for offline/private review, prior to doing a test for which
> results are delivered to W3C.
>
> Selection of a non-default results server could be a configuration item
> which the tester can set at the start of a test session or persistently (eg
> via localstorage).
>
> Bryan
>
> On 8/10/11 1:33 AM, "Francois Daoust"<fd@w3.org>  wrote:
>
>> Hi Philippe,
>>
>> I've added an automatic test results reporting feature to the framework, see:
>>    http://w3c-test.org/framework/suite/nav-timing-default/
>>
>> The page presents a "Report test results automatically (when possible)"
>> checkbox, enabled by default. When activated, pressing "start" will run the
>> test suite, jumping for test case to test case and saving the result reported
>> by "testharness.js".
>>
>> That's a bit ugly from a pure visual point of view as the browser jumps from
>> page to page as soon as it gets the result of the test, but we can improve
>> that later on, I think.
>>
>> Note automatic results reporting gets automatically deactivated when the user
>> chooses to report for a user-agent that is not the user-agent on which it runs
>> the tests.
>>
>> Francois.
>>
>
>
>
Received on Wednesday, 10 August 2011 16:53:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 August 2011 16:53:17 GMT