W3C home > Mailing lists > Public > public-css-testsuite@w3.org > December 2014

RE: 54 new tests submitted in section 3.1

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Tue, 30 Dec 2014 03:46:42 -0500
To: "Zhang, Zhiqiang" <zhiqiang.zhang@intel.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "?? ? (Shiozawa, Hajime)" <hajime.shiozawa@gmail.com>, Public CSS test suite mailing list <public-css-testsuite@w3.org>, Koji Ishii <kojiishi@gluesoft.co.jp>
Message-ID: <f143584dcd3bfec145bb3727cc80803c@gtalbot.org>
Le 2014-12-30 03:38, Zhang, Zhiqiang a écrit :
>> From: fantasai [mailto:fantasai.lists@inkedblade.net]
>> Sent: Tuesday, December 30, 2014 16:01
>> To: Gérard Talbot
>> Cc: "塩澤 元 (Shiozawa, Hajime)"; Public CSS test suite mailing list; 
>> Koji Ishii
>> Subject: Re: 54 new tests submitted in section 3.1
>> 
>> On 12/29/2014 07:43 PM, Gérard Talbot wrote:
>> >
>> >>> Anyway, I will add the float value in the title, as you suggested.
>> >>
>> >> The title should be as concise as possible, but it also needs to be
>> >> sufficiently descriptive to uniquely identify the test. So, as short
>> >> as possible -- but no shorter!
>> >>
>> >> Also, title should just say "CSS Test:", not "CSS Writing Modes Test:".
>> >
>> > Having "Writing Modes" written like in "CSS Writing Modes Test: (...)" is
>> descriptive and contributes to make the test unique:
>> > then, eg., I do not have to edit 'writing-mode' in the rest of the title, just
>> 'vertical-rl' or 'vertical-lr'.
>> >
>> >> We decided not to include the module name to keep it shorter.
>> >
>> > This is news to me. I can read
>> > <title>${1:Test area}: ${2:Scope of test}</title>
>> > http://testthewebforward.org/docs/test-templates.html#reftest-
>> including-metadata
>> > ...which is a bit criptic to me.
>> 
>> I'm not sure where this came from. When I wrote the build scripts, 
>> IIRC
>> were designed to parse the title looking for 'CSS Test:' and replace 
>> it
>> with the name of the built test suite.
>> 
>> Having the module name in the title isn't great; it takes up space 
>> that
>> could say something more specific and useful to identifying what's in
>> the test. If you are testing 'writing-mode', then that can go in the 
>> title.
>> But if you are testing 'unicode-bidi' from the "Writing Modes" module, 
>> then
>> *that* should go in the title.
> 
> Do we need to refine the document,
> http://testthewebforward.org/docs/test-templates.html?
> 
> I take these documents as a formal reference too.
> 
> Happy New Year,
> Zhiqiang

Yes, we should take these documents as a formal reference.

By the way, I'm having a nightmare trying to hg-commit changes and 
hg-merge ... .

$ hg heads

changeset:   6950:f88446e28ffa
bookmark:    master
tag:         tip
parent:      6948:14f7e0e9696e
parent:      6949:8aee821a731a
user:        Zhiqiang Zhang
date:        Tue Dec 30 14:15:28 2014 +0800
summary:     Merge pull request #654 from zqzhang/remove-color-archive

changeset:   6945:cab2042eb775
user:        Gérard Talbot
date:        Tue Dec 30 01:13:21 2014 -0500
summary:     1- inline-replaced-wm-rl-003.xht was filename-renamed


Gérard
-- 
Test Format Guidelines
http://testthewebforward.org/docs/test-format-guidelines.html

Test Style Guidelines
http://testthewebforward.org/docs/test-style-guidelines.html

Test Templates
http://testthewebforward.org/docs/test-templates.html

CSS Naming Guidelines
http://testthewebforward.org/docs/css-naming.html

Test Review Checklist
http://testthewebforward.org/docs/review-checklist.html

CSS Metadata
http://testthewebforward.org/docs/css-metadata.html
Received on Tuesday, 30 December 2014 08:47:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:27 UTC