- From: Tim Boland <frederick.boland@nist.gov>
- Date: Tue, 23 Aug 2005 15:55:02 -0400
- To: www-qa-wg@w3.org
Per my action item from Mon 8-22-05 QAWG teleconference, following are some proposed specific examples for Testcase Metadata [1], to go in the "Example" box for each term. The metadata terms are capitalized, and proposed examples follow, with delimiters separating the terms; the links are at the end. I had some questions (denoted as NOTES) in performing this exercise. I assumed for proposing the examples that the requisite information needs to be present in the test case itself, and not external to the test case (that is, in the test suite). Thanks and best wishes Tim Boland NIST ------------------------------ IDENTIFIER: In CSS1 test case [2], the "14" in the filename refers to Section 1.4 in CSS1 Recommendation - the numbering is unique, in that each test has a different number. NOTE: The CSS2.1 Test Case Authoring Guidelines [3] describes a format for CSS2.1 tests. In MathML test case [4], 'mnScolor8', 'mn' refers to the element being tested, and 'color' indicates testing of the 'color' attribute. NOTE: I'm not sure about the "S" or the "8"; I will try to find out what they mean. ------------------------------ TITLE: In WCAG test case [5], a title appears after the test number, as "Test 1 - All img elements have an alt attribute" , but this may be more of a description than a formal title? NOTE: Is this actually a description? ---------------------------------- DESCRIPTION A possible example is WCAG test case [6]. (see NOTE after TITLE previous). The "mnScolor8" test of the MathML test case [4] also has a description as "tests color attribute inheritance with 'mstyle' and 'mn'. NOTE: This is listed as a "description" but is really a "purpose"? NOTE: What is the exact differentiation between TITLE, DESCRIPTION, and PURPOSE? ------------------------------------------ PURPOSE: In CSS1 test case [7], there is text "This page tests the "text-transform" property of CSS1." Also in the source for CSS2.1 test case [8], there is a title element "CSS2.1: Comments". ------------------------------------------ STATUS: The WCAG test case [5] gives a status of "accepted". ------------------------------------------------ SPECREF: WCAG test case [9], under "WCAG2 Guideline", lists Guideline 1.3 and success criteria of that guideline. CSS1 test case [7] also has a reference to "Specification". -------------------------------------------- PRECONDITIONS: WCAG test case [10] has a prerequisite test that must be run before running this particular test. ------------------------------------------- INPUTS: For Test 2 of UAAG 1.0 test [11], the data "Initial value" in the text box is supplied and is necessary for the test to run correctly; if the user changes this data and activates "reset" the data should go back to "Initial Value". For UAAG test case [12], there is an original value text box, which contains some necessary input data for the test to be run. ------------------------------------- EXPECTEDRESULTS: MathML test case [4] shows default rendering and "your browser's rending" for comparison. CSS1 test case [13] gives expected results in the rendering. CSS2.1 test case [14] gives expected results in the rendering. WCAG test case [5] has an "expected results" item in "test process". Also UAAG test cases [11] and [12] have "expected results" indicated. ---------------------------------- VERSION: UAAG test case [12] has a "last modified" entry with date and author included. NOTE: Is this a sufficient example? --------------------------------------- CONTRIBUTOR: "mnScolor8" of MathML test case [4] indicates "Robert Miner and Jeff Schaefer, Geometry Technologies", as authors WCAG test case [5] has indicated "this test case was created by the ATRC at the University of Toronto". UAAG test case [12], mentions "test created by Dominique Kilman and Colin Koteles" at end. --------------------------------------------- RIGHTS: WCAG test case [5] has a copyright notice included. UAAG test cases [11] and [12] have copyright notices at the end. ---------------------------------------------- GROUPING: CSS2.1 naming conventions in Section 3 of CSS2.1 Test Case Authoring Guidelines [3] allow for selection of certain tests based on section, topic, kind of test, requirement, or file format ---------------------------------------------- SEEALSO: WCAG test case [5] has "comments on this test may be made to (linked) WCAG mailing list" included. UAAG test case [12] has "please send comments on this test to (linked) w3c-wai-ua" included. NOTE: I'm not sure if these qualify as examples in this context? ---------------------------------------------------- [1] http://www.w3.org/QA/2005/08/test-case-metadata.html [2] http://www.w3.org/Style/CSS/Test/CSS1/current/sec14.htm [3] http://www.w3.org/Style/CSS/Test/guidelines.html [4] http://www.w3.org/Math/testsuite/testsuite/Presentation/TokenElements/mn/mnScolor8.xml [5] http://www.w3.org/WAI/GL/WCAG20/tests/test1.html [6] http://www.w3.org/WAI/GL/WCAG20/tests/test57.html [7] http://www.w3.org/Style/CSS/Test/CSS1/current/sec545.htm [8] http://www.w3.org/Style/CSS/Test/CSS2.1/current/t040109-c17-comments-01-b.htm [9] http://www.w3.org/WAI/GL/WCAG20/tests/test121.html [10] http://www.w3.org/WAI/GL/WCAG20/tests/test16.html [11] http://www.w3.org/WAI/UA/TS/html401/cp0101/0101-ACCESSKEY-INPUT.html [12] http://www.w3.org/WAI/UA/TS/html401/cp0102/0102-ONCHANGE-TEXTAREA.html [13] http://www.w3.org/Style/CSS/Test/CSS1/current/sec526.htm [14] http://www.w3.org/Style/CSS/Test/CSS2.1/current/t1503-c522-font-family-00-b.htm
Received on Tuesday, 23 August 2005 19:55:54 UTC