- From: Kris Krueger <krisk@microsoft.com>
- Date: Fri, 3 Sep 2010 01:08:09 +0000
- To: James Graham <jgraham@opera.com>, Anne van Kesteren <annevk@opera.com>
- CC: Philippe Le Hegaret <plh@w3.org>, "public-html-testsuite@w3.org" <public-html-testsuite@w3.org>
Can you change your harness to expose the test result and that the tests have completed running off the window object? Though I updated the test runner to inspect the DOM, exposing the following on the window object would be ideal. -Kris -----Original Message----- From: James Graham [mailto:jgraham@opera.com] Sent: Tuesday, August 10, 2010 9:11 AM To: Anne van Kesteren Cc: Kris Krueger; Philippe Le Hegaret; public-html-testsuite@w3.org Subject: Re: div id="log" On 08/10/2010 06:04 PM, Anne van Kesteren wrote: > On Tue, 10 Aug 2010 18:01:57 +0200, Philippe Le Hegaret <plh@w3.org> wrote: >> one possible improvement: >> >> instead of having maintain the list of tests that are automatic and >> not, why don't you check for id="log" instead? ie, if there is an >> element with id="log" in the test then, it's automatic, otherwise, it's not. > > Even better is probably all tests that include a reference to > testharness.js. Best of all would be all tests :) Checking for something exposed on the window object seems better than inspecting the DOM. For example if one finds add_completion_callback then it is clearly an automated test. There is the question of what to do for e.g. the <canvas> tests that use a different harness.
Received on Friday, 3 September 2010 01:08:48 UTC