- From: SULLIVAN, BRYAN L <bs3131@att.com>
- Date: Thu, 3 May 2012 21:12:47 +0000
- To: Marcos Caceres <w3c@marcosc.com>, Arthur Barstow <art.barstow@nokia.com>
- CC: public-webapps <public-webapps@w3.org>
Marcos, I think it would be great to update the document. While in the Webapps F2F there were some good ideas also floated on supplemental metadata systems (e.g. as used in WHATWG for HTML5) that don't require editors to do anything, IMO we should also consider tooling that helps editors add in class tags or otherwise structure normative statements for more usability as test assertions. Both approaches have merit I believe. The editing tools approach could also be supported through an update to ReSpec, as I have earlier discussed with Robin. Thanks, Bryan Sullivan -----Original Message----- From: Marcos Caceres [mailto:w3c@marcosc.com] Sent: Thursday, May 03, 2012 2:05 PM To: Arthur Barstow Cc: public-webapps Subject: Re: [admin] A Method for Writing Testable Conformance Requirements On Thursday, 3 May 2012 at 19:28, Arthur Barstow wrote: > Editors, All, > > During WebApps' May 2 Testing topic [1], I mentioned the "A Method for > Writing Testable Conformance Requirements" document [2] by Dom and > Marcos. It describes "a method for writing, marking-up, and analyzing > conformance requirements in technical specifications" that could > facilitate test case creation. This is something our new Editors may > want to consider but note the minutes ([1]) also describe some other > methods that could be used. > It's bit out of date, but I'm happy to update it if anyone is interested. -- Marcos Caceres http://datadriven.com.au
Received on Thursday, 3 May 2012 21:13:49 UTC