W3C home > Mailing lists > Public > www-qa-wg@w3.org > August 2003

Re: Revised Guidelines and Checkpoints for TestGL

From: <david_marston@us.ibm.com>
Date: Thu, 21 Aug 2003 12:31:55 -0400
To: QAWG <www-qa-wg@w3.org>
Message-ID: <OF5244579E.A9FA7AC9-ON85256D89.0059CE1F-85256D89.005AD84E@lotus.com>

>> Checkpoint 6.1 Tests should report their status in a consistent
>>manner [Priority 1]
>>Conformance requirements: Tests must report their execution status in
>>a consistent manner. At a minumum, tests should report whether they
>>passed, failed, or whether the results were inconclusive.

DHM>What about speaking about the test suite (test harness?) rather than
DHM>tests? (id for 6.2). 'Tests' seems too fuzzy IMO. Something like:
DHM>"The test harness must report the execution status of the tests in
DHM>a consistent manner".

If we step back and think about what is wanted, I think the informal
statement is:
Regardless of what it is that runs the tests, and regardless of how
many cases in the suite are run, the outcome of each individual test
must be reported in a consistent manner.

From that, we can derive that the test harness (if it both runs tests
and checks results against the "correct" reference results) should
support consistency of reporting. For something like SVG, the harness
may just run all the test cases and present results to a human judge
in a systematic way, and it should also provide a consistent way for
the human to characterize the outcome. This might be a set of buttons
labeled "Pass", "Fail", and "CannotTell", if all the other outcomes
were dealt with by automation before that point. That's as much as
the harness can do to "support consistency of reporting" when a human
makes the call.
.................David Marston
Received on Friday, 22 August 2003 18:56:19 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:14 GMT