- From: Alan Gresley <alan@css-class.com>
- Date: Mon, 04 Nov 2013 11:54:25 +1100
- To: Mihai Balan <mibalan@adobe.com>, "Public CSS Test suite mailing list (public-css-testsuite@w3.org)" <public-css-testsuite@w3.org>
On 4/11/2013 6:23 AM, Mihai Balan wrote: > Hello everybody, [snipped] > However, it proved that the most "interesting" tests were not those > that tested only CSS Regions but CSS Regions *and* X feature (already > standardized or still in work but widely accepted and implemented). > But in writing these tests, I realized they stretch quite a bit the > current definition of what should be a spec tests in a CSSWG spec > test suite - as some people have already pointed out. These tests are > more "feature interoperability" tests than "spec tests". Correct. Interoperability is mentioned often in the overview [1]. Sometimes the spec can not followed since they don't produce interoperability. Sometimes what become interoperable is what the spec becomes. Good test create good specs and good specs create good test. [snipped, someone else could answer much better] > Mihai Balan | Quality Engineer @ Web Engine team | > mibalan@adobe.com<mailto:mibalan@adobe.com> | +4-031.413.3653 / > x83653 | Adobe Systems Romania Be sure to check the current CSS3-regions test suite [2]. Some of this may answer you questions. Alan 1. http://www.w3.org/Style/CSS/Test/Overview.en.html 2. http://test.csswg.org/suites/css3-regions/nightly-unstable/ -- Alan Gresley http://css-3d.org/ http://css-class.com/
Received on Monday, 4 November 2013 00:54:55 UTC