Re: How to handle a Test Suite at W3C Re: Error in (approved) test 0009

This discussion is really useful for the general picture. But let us not
overadministrate ourself. The bug in this test is an absolute clear case
of misspelling, so to say, it is not _at all_ a technically
controversial case and I would not be particularly worried about
changing the test without further notice in that case.

But the situation is not always that easy. My report on test #29:

http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Aug/0033.html

_does_ require some more disciplined procedure indeed.

Ivan



Hausenblas, Michael wrote:
> Karl,
> 
> Thanks for these pointers. If you carefully read one of
> my previous posts [1], I already said that in trying to
> become familiar with testing in W3C, I found some useful
> stuff - first reported in [2].
> 
> I read (did not say understand :) most, if not all of the
> stuff you mention. We do use for example the Test Metadata
> (cf. [3]) etc.
> 
> However, what is missing IMHO are clear instructions how 
> to actually do the test *review*. If I understand Dan correctly
> this is what he is worried about. I know, testing is no rocket 
> science (please do not beat me up, Shane), but anyway, I think 
> we are all after a transparent, unambiguous process and finally 
> want people to implement and use RDFa ...
> 
> Hope that this discussion might trigger a renewal of the
> TC-related stuff at the QA level ... but might also be the case
> that I am too inexperienced with W3C processes and the like :)
> 
> Cheers,
>  Michael
> 
> [1] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Aug/0042.html
> [2] http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007Jan/0049.html
> [3] http://www.w3.org/2006/07/SWD/RDFa/testsuite/Overview.html#ManifestFiles
> 
> ----------------------------------------------------------
>  Michael Hausenblas, MSc.
>  Institute of Information Systems & Information Management
>  JOANNEUM RESEARCH Forschungsgesellschaft mbH
>   
>  http://www.joanneum.at/iis/
> ----------------------------------------------------------
>  
> 
>> -----Original Message-----
>> From: Karl Dubost [mailto:karl@w3.org] 
>> Sent: Monday, August 06, 2007 11:49 PM
>> To: Hausenblas, Michael
>> Cc: Dan Connolly; Ivan Herman; W3C RDFa task force; www-qa@w3.org
>> Subject: How to handle a Test Suite at W3C Re: Error in 
>> (approved) test 0009
>>
>> Hi Michael,
>>
>> Le 7 août 2007 à 04:17, Hausenblas, Michael a écrit :
>>> regarding testing (support)
>>> I really feel left alone within W3C. There are some activities
>>> here (QA) and there, but NO common framework, no best practice,
>>> nothing in the process document AFAIK - how the heck should I know :(
>>
>> What do you need in terms of best practices/framework for Testing?
>>
>>
>> The documents available for now
>>
>> * The QA Handbook
>>   The QA Handbook (QAH) is a non-normative
>>   handbook about the process and operational
>>   aspects of certain quality assurance practices
>>   of W3C's Working Groups, with particular
>>   focus on testability and test topics.
>>
>> * Building a Test Suite
>>   http://esw.w3.org/topic/QA
>>
>> * Test Development FAQ
>>   http://www.w3.org/QA/WG/2005/01/test-faq
>>
>> * Test Metadata
>>   The definition and provision of metadata has
>>   proved helpful in a variety of ways during
>>   the test development and test execution
>>   processes. This document defines a minimal
>>   set of metadata elements that can usefully
>>   be applied to tests that are intended for
>>   publication within a test suite.
>>   http://www.w3.org/TR/test-metadata/
>>
>> * Policies for Contribution of Test Cases to W3C
>>   http://www.w3.org/2004/10/27-testcases
>>
>>
>> -- 
>> Karl Dubost - http://www.w3.org/People/karl/
>> W3C Conformance Manager, QA Activity Lead
>>   QA Weblog - http://www.w3.org/QA/
>>      *** Be Strict To Be Cool ***

-- 

Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf