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

[Bug 15062] Test results appearing in other test suites

From: <bugzilla@jessica.w3.org>
Date: Tue, 06 Dec 2011 16:49:17 +0000
To: public-test-infra@w3.org
Message-Id: <E1RXyCj-0003jC-QY@jessica.w3.org>

--- Comment #9 from Richard Ishida <ishida@w3.org> 2011-12-06 16:49:16 UTC ---
> First, you need to remove your section data, this is only for sections of
> specs, not of test suites. 
> Second, you need Mike to set up the proper format data in the framework, there
> is currently only one HTML format: 'html', you need separate formats listed for
> each of your test formats, ie: HTML4, HTML5, etc. 

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=15061

> Third, ensure the proper spec section data is loaded for the specs you are
> testing: ie: HTML4, HTML5 etc. 

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=15079

> Then make sure your test suites are set up properly, ie: the i18n-HTML4 test
> suite lists only the tests in HTML4 format, 

Already the case. 

>linked to the relevant sections of
> the HTML4 spec and using the HTML4 format identifier;

Waiting for action on the above two bugs before I can do that for HTML4. 

> the i18n-HTML5 test suite
> lists only the tests in HTML5 format, linked to the HTML5 spec, using the HTML5
> format identifier, etc.

This is now all done for the html5 tests. I had the mechanism in place, but was
waiting to transition to it. The spec indexes were intended to be a temporary
thing until I was confident that things should work the way they are intended,
and to enable me to do some testing.

> The test suites you are creating are really sub-sections of the HTML4, HTML5,
> etc test suites that deal with i18n issues. The tests in those suites will be
> listed by the sections of the specs they are testing, and any results gathered
> will be shared with other test suites that use the same tests (like a full
> HTML5 test suite).

One thing that I was (and to an extent still am) unsure about is that the i18n
tests are often exploratory or test things that are not required by the spec at
all. For now, i have aligned those tests with sections that contain related
information.  I assume that those tests will be ignored if the HTML5 (or other)
WG decides that they want to import our tests to their test suite.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 6 December 2011 16:49:24 UTC

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