W3C home > Mailing lists > Public > public-css-testsuite@w3.org > November 2013

Re: What *is* a spec test? (musings on feature interop tests)

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Wed, 27 Nov 2013 13:59:24 -0500
To: Mihai Balan <mibalan@adobe.com>, Peter Linss <peter.linss@hp.com>
Cc: Tobie Langel <tobie@w3.org>, Alan Gresley <alan@css-class.com>, Ms2ger <ms2ger@gmail.com>, "Public CSS Test suite mailing list (public-css-testsuite@w3.org)" <public-css-testsuite@w3.org>
Message-ID: <277a356c1619a56c14c257478ca7cb53@gtalbot.org>
Le 2013-11-27 04:57, Mihai Balan a écrit :
> Answers inline.
> Mihai Balan | Quality Engineer @ Web Engine team |  mibalan@adobe.com |
> +4-031.413.3653 / x83653 | Adobe Systems Romania
> On 11/26/13 9:11 PM, "Gérard Talbot" <css21testsuite@gtalbot.org> 
> wrote:
>> Le 2013-11-26 09:15, Mihai Balan a écrit
>>> [snip]
>>> Or does the build step for test suites includes all the tests that
>>> reference a particular spec (section)?
>> Yes. Peter Linss should confirm this. In your example, it should 
>> create
>> a test in regions and in fragmentation.
> Makes sense and it sounds like good news :)

Peter has to confirm this.

Also, note that there is *not yet* a CSS3 fragmentation src folder and 
there is *not yet* a CSS3 fragmentation test suite.




(click the "All Specifications" drop-down list to expand it)

> However, what about if some of the specs linked to are not CSS specs?
> Would the test still be part of the other spec test suite? (e.g. if I'm
> writing a test for CSS Regions and ShadowDOM)

My answer is no (at least not automatically): the test would not become 
part of the other spec test suite ...unless Web Applications Working 
Group people contact Peter Linss and then reach an agreement to do this.

There is a shadow DOM Working Draft.
And so, it's not illogical to create or have a test suite for Shadow DOM 
one day.

For now, you can just add a link like this (eg):

<link rel="help" 
title="5.2 Retargeting relatedTarget">

Again, Peter Linss should confirm this.


> these tests are useful and they should
> not be separated rather be tracked as parts of test suites they appear 
> in.

Peter Linss should answer you. If a test is supposed to be in 2 distinct 
and already-existing CSS test suites (say, CSS3 multi-column and CSS3 
Text), then the build system should be smart enough to create the same 
test in the appropriate sections of those 2 respective CSS test suites. 
Peter Linss has to instruct the built system to do this.

but there is no CSS3 values test suite created yet.

Adding Peter Linss as email recipient.

Web authors' contributions to CSS 2.1 test suite
CSS 2.1 Test suite RC6, March 23rd 2011
Received on Wednesday, 27 November 2013 18:59:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:20 UTC