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

Re: [RC3] Multiple rendering references for testcases: eg block-in-inline-*

From: L. David Baron <dbaron@dbaron.org>
Date: Sat, 20 Nov 2010 14:15:37 -0800
To: "Gérard Talbot" <css21testsuite@gtalbot.org>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <20101120221537.GA16037@pickering.dbaron.org>
On Saturday 2010-11-20 13:44 -0800, "Gérard Talbot" wrote:
> I am confused about how "Rendering References" are supposed to work.
> 
> E.g.:
> 
> http://test.csswg.org/suites/css2.1/20101027/html4/block-in-inline-insert-001a.htm
> 
> has 2 rendering references:
> 
> http://test.csswg.org/suites/css2.1/20101027/html4/block-in-inline-insert-001-nosplit-ref.htm
> 
> http://test.csswg.org/suites/css2.1/20101027/html4/block-in-inline-insert-001-ref.htm
> 
> and those 2 differ.
> 
> If you examine
> http://test.csswg.org/suites/css2.1/20101027/html4/chapter-9.html#s9.2.1.1
> you will see that several testcases have 2 rendering references as well.
> Same thing with RC1 (20100917):
> http://test.csswg.org/suites/css2.1/20100917/html4/chapter-9.html#s9.2.1.1
> 
> How is it that all implementation reports can then report that they fail
> or pass a test with 2 different rendering references?

In the normal use of reftest, each pair of files constitutes a test
(typically referred to as the test and the reference, though these
names really only refer to which of the two files uses the feature
the author was trying to test and which of the two files uses some
other feature, which is often also worth testing).  This permits
construction of a second test using one of the files also in another
pair, along with a third file.

However, the reftests that have been contributed were incorporated
into the test suite on the assumption that the test and reference
names were exact, and every test should have exactly one reference.
This isn't an unreasonable rule, but it wasn't one that I was aware
of at the time Mozilla contributed the tests.

Probably the pairings of the tests should be adjusted to match this
assumption.

> Sometimes/often, the rendering references have validation markup errors
> too.

That seems like a separate issue worth reporting.

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
Received on Saturday, 20 November 2010 22:16:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 20 November 2010 22:16:26 GMT