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

Re: Comments on XHTML Form test cases

From: Wilhelm Joys Andersen <wilhelmja@opera.com>
Date: Tue, 18 Dec 2007 16:20:10 +0100
To: public-mwts <public-mwts@w3.org>
Message-ID: <op.t3jd7wcwm3w6te@kugalskapet>

* Dominique Hazael-Massieux <dom@w3.org> wrote:
|  * the test cases should explain more clearly what the user should (or
| should not) see, and what (if any) operations she's supposed to do; some
| tests have this, but most don't


The text on the test could also be simplified significantly to make life  
of the tester (who is perhaps labelling the results of hundreds or  
thousands of tests) a bit easier.

One test says:

    Form element - Test FORMS-NIST-003

    This test examines the FORM element with the attribute METHOD set
    to "post" and usage of "INPUT" element with TYPE = "checkbox".

If the intention is to test that the checkbox form element is working, I'd  
rewrite this to say:

    An unchecked checkbox should be visible below:

    [ ]

The text "FORMS-NIST-003" should be moved to the <title>, along with a  
very short description of what is tested.

We should also have a test testing that the checked checkbox is displayed  

    A checked checkbox should be visible below:


The two proposed tests above would be visual and easy to make part of  
automated testing. Six interactive tests testing the checkbox input type  
should also be part of this testsuite to get full test coverage.

One for testing changing the checkbox using your mouse (or pen or Wiimote  
or other poiting device):

    Click the checkbox below twice with your pointing device. It
    should become checked the first time you click it, and
    unchecked the second time you click it.

    [ ]

One for testing the same using a keyboard.

And four tests for form submission:

    Submit this form. You should see the word "PASS".



Two for checked checkboxes (one with GET, one with POST) and two for  
unchecked checkboxes. The output should be checked using a server-side  
script which then should output "PASS" or "FAIL". If possible, a  
client-side script should submit the form automatically so that the tester  
does not have to do anything but labelling the result.

Similar changes should be made to all relevant tests in this testsuite.

| * most of the test where the mention of the attribute method being set
| to POST don't need that information; in fact, it's probably more natural
| to use "GET" by default rather than POST

Both should be tested in the case of form submission.

Wilhelm Joys Andersen
Core QA, Opera Software
Received on Tuesday, 18 December 2007 15:20:13 UTC

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