action-122: Tests description for BP

Hello everybody,

Newton and I worked in the action 112: Research and report ways that 
technical best practices have been tested.

We have read tests in two documents: Mobile Web Best Practices 1.0 and 
Web Content Accessibility Guidelines (WCAG) 2.0.

In the Mobile Web Best Practices the tests for best practices are 
structured in a section called What to Test and it shows if the test is 
machine testable or human testable. One example of test case in this 
document is:

[ACCESS_KEYS] Assign access keys to links in navigational menus and 
frequently accessed functionality.
*What to test*
*Machine Test*: Test for the presence of the accesskey attribute.
*Human Test*: Verify the presence of the accesskey attribute on links 
such as the home page.

In the Web Content Accessibility Guidelines (WCAG) 2.0 the tests for 
guidelines are structured in two items: procedures (step-by-step) and 
expected results. One example of test case in this document is:

H75: Ensuring that Web pages are well-formed 
(http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/H75.html)
*Tests*
*Procedure*

    1. Load each file into a validating XML parser.
    2. Check that there are no well-formedness errors.

*Expected Results*

    Step 2 is true.
    If this is a sufficient technique for a success criterion, failing
    this test procedure does not necessarily mean that the success
    criterion has not been satisfied in some other way, only that this
    technique has not been successfully implemented and can not be used
    to claim conformance.


We want to propose the following structure to make the tests description:

    Best Practice: number and description
    Classification: Machine Test, Human Test (or even both)
    Procedure to test (in steps)
    Expected Results (for tests)

What do you think about this proposal?


-- 
NIC.br | Nathalia Sautchuk Patrício
Assessora Técnica
Diretoria de Assessoria às Atividades do CGI.br
+55 11 5509-3537R.: 4072
www.nic.br <http://nic.br>