QA WG Test Task Force Charter

Draft, January 21, 2003

Editor: Dimitris Dimitriadis

Mission Statement

The mission of the QA WG Test Task Force (TTF) is to ensure that guidelines in the QA test guidelines documents are put into practice by W3C Working Groups.

Scope and Deliverables

The TTF scope is to:

• Ensure the use of practices required by the QAWG Guideline documents.
• Provide technical expertise to assist and support W3C Working Groups in providing Test Materials for their specifications.
• Find tools that implement the QAWG Guideline techniques and where there are none, prototype or participate in the development of a tool.

In addition, the TTF produces in association with others or on its own, Test Frameworks to ensure that test materials produced in the W3C Working Groups can be used, where applicable, by others.

The TTF deliverables are:

• Provide information on existing Test Technologies and techniques used and developed by Working Groups in the W3C and other interested parties (information can be documents, tutorials, web sites and so forth)
• Provide on-demand expertise to Working Groups seeking to produce such materials
• Assure uniformity in Test Frameworks and Techniques produced, as explained in other QA WG documents (ensure that tools conforming to QA WG Test Guidelines documents are used and, where applicable, reused by as many WG as possible).
• Develop tools and tool kits of general usefulness to help WGs develop test materials.

It is desirable that the Test Task Force build tools (test materials), resources allowing.

Duration

The TTF should be chartered with general W3C needs in mind, for example, two-year periods, renewable if necessary. It is anticipated that the TTF be active for at least two years.

Success Criteria

Ensure that guidelines in the QA Testing guidelines Document get followed by other Working Groups in the W3C.

Milestones

[@ed: tbd]

Confidentiality and Intellectual Property Rights (IPR)

[@ed: tbd]

Dependencies/Relationship with other W3C Activities

It is fair to assume that the interrelationships with the QA WG are to be very strong. However, relationships with other Working Groups can be envisioned, especially those more technical/architectural in orientation.

Coordination with External Groups

As proposed, the TTF should communicate directly with other W3C Working Groups, not through a regular Interest Group setup.

Communication Mechanisms

Email

The TTF should have an archived mailing list [@ed: not sure if it should be public, though, as some discussions that will take place will be about member-confidential material, such as not yet released specifications]

Web

The TTF should have a Web Page

Phone Meetings

If invited to participate in Working Group activities, a separate agenda should be set up. No regular telephone conferences are envisioned.

Face-to-Face meetings

As for the Phone meetings

Voting Mechanisms

If applicable, by consensus.

Participation

This is subject to discussion within the W3C as financing will be required (either to have W3C staff work on this, or by inviting external experts/resources)

How to join the WG

N/A