RE: draft How To Guide for Test Assertions

Hi Christophe
Glad that you are interested.  The work that you have done will help to
add another perspective as we go forward.  For now, there are some
logistics to work out with respect to working with OASIS.  However, that
won't stop us from getting started.  So, soon, I hope to circulate a
draft outline and initial thoughts.  

Welcome aboard
--Lynne



> -----Original Message-----
> From: www-qa-request@w3.org [mailto:www-qa-request@w3.org] On Behalf
Of
> Christophe Strobbe
> Sent: Thursday, March 02, 2006 5:15 AM
> To: www-qa@w3.org
> Subject: Re: draft How To Guide for Test Assertions
> 
> 
> Hello Lynne,
> 
> At 13:50 1/03/2006, Lynne S. Rosenthal wrote:
> <blockquote>
> The QA IG will be working with members of OASIS to develop a
How-to-Guide
> or Dummy's guide on Test Assertions.  This was discussed during the
QAIG
> meeting at Tech Plenary on Monday, 27 February.  The work will
conducted
> under both the W3C and OASIS banners (details on how to do this are
being
> ironed out), lead by Lynne Rosenthal (NIST) and Jacques Durand
(Fujitsu),
> and hopefully, with your help.  Please let us know if you would like
to
> participate in this effort.  It should be fun, since it will be a
> practical
> guide, capturing experiences, and written in a light, readable, style.
> (...)
> </blockquote>
> 
> I am currently involved in a project (www.bentoweb.org) that is
working on
> an XHTML + CSS test suite for Web Content Accessibility Guidelines
2.0.
> The
> "test suite" is not really a suite of tests in the usual sense, but a
set
> of test files + metadata that is meant to be used to "benchmark"
> evaluation
> and repair tools ("ERT": http://www.w3.org/WAI/ER/existingtools). How
to
> write the description, purpose and other sections of the test metadata
(we
> use most of the test metadata described at
> http://www.w3.org/TR/2005/NOTE-test-metadata-20050914/, and much more)
was
> recently the subject of serious debate, which led us to rewrite the
> description and purpose of all our tests. In our test metadata, the
"test
> assertion" is actually part of the purpose, and the position where a
> failure occurs (line & column number, XPath) is mentioned elsewhere.
> I'm very interested in this 'How To Guide for Test Assertions'; maybe
I
> will also be able to contribute to it.
> 
> Regards,
> 
> Christophe Strobbe
> 
> 
> --
> Christophe Strobbe
> K.U.Leuven - Departement of Electrical Engineering - Research Group on
> Document Architectures
> Kasteelpark Arenberg 10 - 3001 Leuven-Heverlee - BELGIUM
> tel: +32 16 32 85 51
> http://www.docarch.be/
> 
> 
> Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
> 
>

Received on Friday, 3 March 2006 12:43:06 UTC