- From: Scheppe, Kai-Dietrich <k.scheppe@telekom.de>
- Date: Tue, 7 Feb 2012 11:43:38 +0100
- To: "public-w3process@w3.org" <public-w3process@w3.org>
What about actually getting specs involved with the Web testing activity? For example, in order to finish a spec a WG MUST provide appropriate, deterministic test cases in the Web testing space. I think this would be very useful as it shifts the burden of "interpreting" a certain fuzzyness of a spec from the implementer to the author. Plus it provides actual test cases that contribute to the overall volume of test cases available. -- Kai > -----Ursprüngliche Nachricht----- > Von: Karl Dubost [mailto:karld@opera.com] > Gesendet: Montag, 6. Februar 2012 19:48 > An: Marcos Caceres > Cc: Charles McCathieNevile; public-w3process@w3.org > Betreff: Test Driven Specification Re: "Living Standards" > > :) > > Le 6 févr. 2012 à 13:27, Marcos Caceres a écrit : > > I guess my point was that . perhaps. linking tests to specs needs to > be a more explicit part of the process. > > > Worth pushing. Be ready for plenty of frustrations. > > Having tests in the specification is indeed a way to raise the bar of > quality. We just pushing further the envelope of quality. It will not > solve the issues as in once we reached that stage we will want to push > further. Been there, done that (with Candidate Recommendation created, > conformance section, interop reports, etc.) > > It also means by pushing that we add another layer of. process (being > written or not ;) still the same). Personally, I don't mind, I know > some vocal WG participants do mind :) Life is not easy. > > > -- > Karl Dubost - http://dev.opera.com/ > Developer Relations, Opera Software >
Received on Tuesday, 7 February 2012 10:49:14 UTC