- From: Jonathan Griffin <jgriffin@mozilla.com>
- Date: Mon, 30 Nov 2009 11:58:33 -0800
- To: Kris Krueger <krisk@microsoft.com>
- CC: "'public-html-testsuite@w3.org'" <public-html-testsuite@w3.org>, "Michael(tm) Smith" <mike@w3.org>
It's hard for me to wrap my head around what kinds of metadata we'll need and how it should be stored without seeing the larger picture. We know there are existing tests for many parts of HTML5 in various places; I think it would be helpful to collect these on a wiki somewhere for review: - how suitable are they for inclusion into an official HTML5 test suite? - how much work will they take to cleanup and extend? - if they're not automated, will we automate them, and how? - will we try to tie them all together with a common test runner (e.g., http://omocha.w3.org/wiki/)? - do we want to manage storage of test results, e.g., in a SQL or CouchDB server? Having the answers to these questions might take care of some of these metadata questions, or at least provide some framework for answering them. Regards, Jonathan Kris Krueger wrote: > I'd like to get agreement on a test case template for the HTML testing task force. > To start with I'd like to propose that the template allow for including other key information about the test using a meta tag. > > For example a test case that depends upon the ahem font would contain. > > <meta name="flags" content="ahem" /> > > Other key information that may been necessary > > Author -> Who created the test > Status/Phase -> Approved/Draft/Submitted > Reviewer -> Who reviewed the test case > Help -> URI back to the specification > Assert -> Describes what specifically the test case tests > > Thoughts? Other additional information that we would like to have? > > -Thx > > > > > > > > > > >
Received on Tuesday, 1 December 2009 08:31:48 UTC