W3C home > Mailing lists > Public > public-mwts@w3.org > May 2007

Re: [agenda] Tuesday May 29 teleconf

From: Wilhelm Joys Andersen <wilhelmja@opera.com>
Date: Wed, 30 May 2007 18:25:00 +0200
To: public-mwts@w3.org
Message-ID: <op.ts5ejygem3w6te@kugalskapet>

* Dominique Hazael-Massieux <dom@w3.org> wrote:
| ACTION: Wilhelm to submit example test cases for guidelines document
| [recorded in http://www.w3.org/2007/05/22-mwts-minutes.html#action11]

Here are some test cases we can use as examples of good tests:

   * http://www.hixie.ch/tests/adhoc/html/bidi/001.html
   * http://www.hixie.ch/tests/adhoc/css/box/block/first-line/001.html
   * http://www.hixie.ch/tests/adhoc/css/box/table/010.xml
   * http://www.hixie.ch/tests/adhoc/css/box/block/text-indent/001.html

As mentioned during this week's meeting, I have some additional
suggestions for test case guidelines. These are based on Opera's (more
verbose) internal guidelines, and make the life of testers significantly
less painful.

Here goes:

   * Test cases should have a clear pass condition and
     indicate in the simplest way possible whether it has
     passed or failed. “The word 'PASS' should appear
     below” is a good positive pass condition. “There should
     be no red on this page” is a good negative pass
     condition. Using colours or the words 'PASS' and 'FAIL'
     to indicate success or failure is encouraged.

   * When using colour to indicate success or failure, use
     green for success and red for failure. Avoid using these
     colours for any other purpose, as this could cause
     confusion. Blue, orange, yellow and teal are neutral
     colours useful for comparision tests (“Two identical
     blue rectangles should appear below”).

   * Metadata should be left out of the test itself. The
     <title> of the test should describe what feature is
     tested. How the test is performed should be self-evident
     when viewing its source code.

   * Each test case should just test one thing. Avoid
     composite tests.

Wilhelm Joys Andersen
Core QA, Opera Software
Received on Wednesday, 30 May 2007 16:25:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:08:01 UTC