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

Re: Automatic test results reporting

From: Bryan Sullivan <blsaws@gmail.com>
Date: Wed, 10 Aug 2011 06:19:58 -0700
To: Francois Daoust <fd@w3.org>, Philippe Le Hegaret <plh@w3.org>
CC: public-test-infra <public-test-infra@w3.org>
Message-ID: <CA67D38E.12ED1%blsaws@gmail.com>
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). 


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 13:20:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:32 UTC