W3C home > Mailing lists > Public > public-wai-ert@w3.org > March 2005

Re: EARL and describing tests Re: Agenda for F2F at TP

From: Karl Dubost <karl@w3.org>
Date: Thu, 10 Mar 2005 18:01:36 -0500
Message-Id: <1cb8d753d5ee7c5fc82feb2c6537da44@w3.org>
To: public-wai-ert@w3.org

Le 08 mars 2005, à 10:01, Charles McCathieNevile a écrit :
> I think Jim is right that we need to be able to identify tests, and 
> provide at least basic descriptions of them.

Identifying the test makes completely sense and the first thing which 
comes to mind is a URI.

Description of the test seems something more difficult to handle by the 
nature itself of testing. I would expect that when I know the URI I 
have a way to retrieve the description information. I'm not sure about 
the requirement of having it _into_ EARL.

Practical example:

Story: I'm going out only if the temperature is +25°C, it's sunny, and 
it's sunday.

Question:
	Assertion: Do you go out? <URI_assertion>
		Test 1: if T > 25 -> yes, if T < 25 -> no
		Test 2: if W = sun -> yes, if W = rain -> no
		Test 3: if D = sunday -> yes, if D = Monday, ..., Saturday -> no
	
	Report: (EARL)
		Assertion yes, no, comment

So the basic thing to know is that is the purpose of EARL to report the 
result of passing a test case, or to report the answers to a number of 
assertions.
	(Sometimes assertions can be test cases, BUT it's not necessary always 
the case, depending on what you want of EARL).



-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***

Received on Friday, 11 March 2005 04:46:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:25 GMT