W3C home > Mailing lists > Public > public-html-testsuite@w3.org > January 2010

RE: HTML Testing Task Force Conf Call Agenda 1/12/2010

From: Kris Krueger <krisk@microsoft.com>
Date: Thu, 28 Jan 2010 16:38:11 +0000
To: Larry Masinter <masinter@adobe.com>
CC: "'public-html-testsuite@w3.org'" <'public-html-testsuite@w3.org'>
Message-ID: <3607818D324EC04E8767AA21E274C023202AB8A6@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Good questions, though I think when one submits a tests they should add to the cvs log the section and date of the html5 spec will cover all of these issues.

-Kris


-----Original Message-----
From: Larry Masinter [mailto:masinter@adobe.com] 
Sent: Monday, January 11, 2010 7:34 PM
To: Kris Krueger
Cc: 'public-html-testsuite@w3.org'
Subject: RE: HTML Testing Task Force Conf Call Agenda 1/12/2010

How do you like features to sections of the specification?

Does the reorganization of the specification interfere with deciding what you are testing?
Are tests linked to any particular date of the specification? What if the specification changes, how will you like that to test changes?

Should test cases contain a version identifier, which might be useful to identify which version of which specification was being consulted when the test case was written?

Would it be useful if a test case used that version identifier, say, in the <!DOCTYPE> header?


Larry
--
http://larry.masinter.net


-----Original Message-----
From: public-html-testsuite-request@w3.org [mailto:public-html-testsuite-request@w3.org] On Behalf Of Kris Krueger
Sent: Monday, January 11, 2010 7:24 PM
To: 'Geoffrey Sneddon'
Cc: 'public-html-testsuite@w3.org'
Subject: RE: HTML Testing Task Force Conf Call Agenda 1/12/2010

Sure - 

As mentioned at the previous conf call, until we move away from CVS :)
tests should be submitted under /html5/tests/submissions/[SUBMITTER]/[FEATURE]/tests...

The [SUBMITTER] is your name or company
The [FEATURE] should be the name of the feature and not the chapter, for example parser and not chapter_7.2.

Once we agree that A) the spec is complete or reasonably stable for a given feature and B) we have tests that we agree test the feature we can move them to an approved folder.  Because we are still in CVS I'll track tests the using a spreadsheet saved in CVS that can be opened in open office version 3 and Excel.

-Kris

-----Original Message-----
From: Geoffrey Sneddon [mailto:gsneddon@opera.com] 
Sent: Monday, January 11, 2010 3:37 AM
To: Kris Krueger
Cc: 'public-html-testsuite@w3.org'
Subject: Re: HTML Testing Task Force Conf Call Agenda 1/12/2010

Kris Krueger wrote:
> Agenda Items
> 
> #1 Status Review For Action Items (#1 -> #4)
> #2 Review Test Submission Process (e.g. from a test submitted to cvs -> 'approved')
> #3 Discuss where we want to be at 6 months from now
> 
> For #2 the initial example would use a set of cross-domain test cases submitted by Microsoft.
> The test cases work in IE8, Opera 10, Firefox3.5, Safari 4 and the spec itself looks quite 'stable'.

Could you send out a description of the test submission process by email 
before the telcon? I'd rather not have to be working out my own opinion 
in real-time. :)

-- 
Geoffrey Sneddon - Opera Software
<http://gsnedders.com/>
<http://www.opera.com/>
Received on Thursday, 28 January 2010 16:38:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 28 January 2010 16:38:51 GMT