W3C home > Mailing lists > Public > public-webapps-testsuite@w3.org > June 2012

Selectors API testsuite now using testharness.js

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Fri, 29 Jun 2012 15:23:45 +0200
Message-ID: <4FEDAC61.9040806@lachy.id.au>
To: public-webapps-testsuite@w3.org
   I have ported the old Selectors API testsuite to the new framework.

The new tests are structured similarly to the old tests, but named 

The files named *-frame.* are support files loaded in iframes by the 
tests. They include the CSS and HTML necessary for the tests.  The other 
files each load one of these in an iframe and run the selector tests on 

The following changes have been made in all tests relative to the old 
test suite.:
1. No parameter tests now explicitly requires that a TypeError is
    thrown. The old test suite accepted any exception as a pass.
2. All tests now have a unique description, necessary for automated

* level1-baseline.html

Selectors API Level 1 baseline tests.  These are HTML with CSS level 2.1 
selectors.  The coverage is similar to 001.html from the old testsuite.


The differences are:
1. The any-namespace and no-namespace tests have been added as baseline
    tests.  These are the same as those in the old 002.html tests.

* level1-additional.html

Selectors API Level 1 baseline+additional tests. These are HTML with 
Selectors Level 3.  The coverage is similar to 002.html from the old 


The changes are:
1. New input:disabled tests were added. This causes some :disabled
    tests that existed in the old test suite to now fail.
2. Some input:enabled tests were added.
   (Note: these did actually exist in the old tests, but were
    previously commented out. They have now been uncommented in the old
    tests too.)

* level1-xhtml.xht

Selectors API Level baseline+additional XML tests.  These are XHTML and 
SVG with Selectors Level 3


The differences are the same as level1-additional.html

* level2-baseline.html

This covers only new features added to Selectors API Level 2.  It 
currently only includes a few tests for matchesSelector.  This 
incorporates tests for implementations with prefixed method names 
(oMatchesSelector, mozMatchesSelector, etc.)

This will use Selectors Level 3 plus at least :scope from Selectors 4, 
but these tests aren't fully written yet.


Lachlan Hunt - Opera Software
Received on Friday, 29 June 2012 13:24:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:52:56 UTC