- From: Peter Linss <peter.linss@hp.com>
- Date: Tue, 25 Jun 2013 10:38:39 -0700
- To: L. David Baron <dbaron@dbaron.org>
- Cc: Rebecca Hauck <rhauck@adobe.com>, www-style list <www-style@w3.org>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
On Jun 24, 2013, at 8:42 PM, L. David Baron wrote: > On Monday 2013-06-24 16:30 -0700, Rebecca Hauck wrote: >> 1. Add the Test Suite section to all of the specs – those with no tests labeled "none yet" >> 2. Link to the test suite cover page per fantasai's suggestion > > There should be instructions somewhere on how to cause such a test > suite cover page to exist for a new spec. Part of the reason I > wrote "none yet" was because I couldn't (I think) do it myself, and > it didn't seem worth bothering somebody else about when there > weren't any tests yet. The cover page is generated by the test suite build process. Currently that requires a manual setup on the server, but I'm currently working on making it fully automatic. So soon test suites will just start appearing as soon as there are tests linked to that spec in the repo. > > I think the cover page should also link to existing results for the > tests (which is why I had two links in one spec, I suspect), though > we should also start gathering such existing results through > automation rather than encouraging manual running of the tests. I can add a link to the harness in the cover page. The spec should also have the annotations script which will add links to the harness directly in the spec. Peter > > -David > > -- > 𝄞 L. David Baron http://dbaron.org/ 𝄂 > 𝄢 Mozilla http://www.mozilla.org/ 𝄂 >
Received on Tuesday, 25 June 2013 17:39:01 UTC