- From: Zhiheng Wang <zhihengw@google.com>
- Date: Thu, 2 Dec 2010 14:08:35 -0800
- To: Sigbjørn Vik <sigbjorn@opera.com>
- Cc: public-web-perf@w3.org
Received on Thursday, 2 December 2010 22:09:07 UTC
On Thu, Dec 2, 2010 at 12:32 AM, Sigbjørn Vik <sigbjorn@opera.com> wrote: > On Wed, 01 Dec 2010 20:45:44 +0100, Anderson Quach < > Anderson.Quach@microsoft.com> wrote: > > AndersonQuach: feedback, we should include: title of tests, description of >> tests, objective, and clear pass / fail criteria. >> ... would recommend that we pursue self-contained tests until we need a >> common infrastructure for testing async behavior and etc. >> > > I agree with self-contained, but using the standard harness is also good, > as this allows us to integrate the tests into our framework without touching > the test itself, we just replace the harness with our own. Not quite sure if > that was mentioned. For the same reason, it would be good if tests used > relative paths from the root (/resources/testharness.js) instead of absolute > paths (http://test.w3.org/resources/testharness.js). > Good idea. I've changed the test and also added local copy of the harness files. cheers, Zhiheng > > -- > Sigbjørn Vik > Quality Assurance > Opera Software > >
Received on Thursday, 2 December 2010 22:09:07 UTC