W3C home > Mailing lists > Public > public-html-testsuite@w3.org > August 2010

RE: getElementsByClassName approval/feedback request

From: Kris Krueger <krisk@microsoft.com>
Date: Wed, 4 Aug 2010 23:47:04 +0000
To: James Graham <jgraham@opera.com>
CC: "'public-html-testsuite@w3.org' (public-html-testsuite@w3.org)" <public-html-testsuite@w3.org>
Message-ID: <FA9085650D2F8B4A9D501ED9D9706E9A126026BB@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
> We just submitted some getElementsByClassName tests in http://test.w3.org/html/tests/submission/Opera/getElementsByClassName/
Great - Lets have these tests approved at the next meeting assuming no one find the tests invalid per the spec.

> Also, I added a empty testharnessreport.js file. The idea is that we could use this for test runner integration and browser vendors can use it to interface with whatever systems they have for running tests. I suppose it is also possible to insist that all tests run in an iframe, but this could be difficult if we want to test the behaviour of window.top for example. Having said that I don't really know how to automate running the tests in an entirely transparent way, so maybe an iframe is enough and this is unneeded. Thoughts?

I'll take a peek at integrating this into the test runner, this is basically what we discussed at the last conf call.

-Kris

-----Original Message-----
From: James Graham [mailto:jgraham@opera.com] 
Sent: Tuesday, August 03, 2010 8:28 AM
To: Kris Krueger
Cc: 'public-html-testsuite@w3.org' (public-html-testsuite@w3.org)
Subject: Re: getElementsByClassName approval/feedback request

On 07/22/2010 04:21 AM, Kris Krueger wrote:
> Microsoft created and submitted tests for 'getElementsByClassName' as 
> we have been developing IE9.
>
> I'd like to have these tests approved, if you think that they are 
> wrong per the spec please provide feedback.
>
> http://test.w3.org/html/tests/submission/Microsoft/apis/

We just submitted some getElementsByClassName tests in http://test.w3.org/html/tests/submission/Opera/getElementsByClassName/

As a side point, if there are generic files that we expect to be reused across multiple tests, it would be nice to have a generic place to put them so that they end up in the same place in submitted/ and approved/ and we don't end up with multiple copies of the same file scattered about the place.

Also, I added a empty testharnessreport.js file. The idea is that we could use this for test runner integration and browser vendors can use it to interface with whatever systems they have for running tests. I suppose it is also possible to insist that all tests run in an iframe, but this could be difficult if we want to test the behaviour of window.top for example. Having said that I don't really know how to automate running the tests in an entirely transparent way, so maybe an iframe is enough and this is unneeded. Thoughts?
Received on Thursday, 5 August 2010 04:49:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 5 August 2010 04:49:54 GMT