W3C home > Mailing lists > Public > www-qa@w3.org > October 2003

Final Minutes for QA WG meeting 2003-09-29

From: VANITHA VENKATRAMAN <Vanitha.Venkatraman@Sun.COM>
Date: Wed, 15 Oct 2003 14:02:04 -0700
To: www-qa@w3.org
Message-id: <3F8DB5CC.1060008@Sun.COM>

QA Working Group Teleconference
Monday, 29-September-2003

Scribe:Vanitha Venkatraman

(PC) Patrick Curran (Sun Microsystems)
(KD) Karl Dubost (W3C, WG co-chair)
(DH) Dominique HazaŽl-Massieux (W3C)
(LR) Lynne Rosenthal (NIST - IG co-chair)
(DM) David Marston (IBM)
(MS) Mark Skall (NIST)
(VV) Vanitha Venkatraman (Sun Microsystems)

(PF) Peter Fawcett (RealNetworks)
(LH) Lofton Henderson (CGMO - WG co-chair)
(MS) Mark Skall (NIST)

(dd) Dimitris Dimitriadis (Ontologicon)
(KG) Kirill Gavrylyuk (Microsoft)
(AT) Andrew Thackrah (Open Group)

1) roll call 11am EDT, membership
Please see above to attendee list

2.) QA Ops GL CR  [2]
    - Implementation Plan for CR [3]:     OWL and WAI
    - Organizing reviews of WGs to find implementation [4]
        Late. Today.
    - Selling Points of QA Ops Doc
Notes: Still missing salient points for the QA Ops.

3.) TestGL topics (continued) [5]
    - Patrick Curran continues the discussion about TestGL

Notes from meeting:

Areas Discussed: metadata, coverage, tracking last chkpt for GL#3
Question: Do you need extra chkpt for GL#3
GL#3 could conflict with GL#7

Discussed GL#4 - Test Execution at length.
Different options - golden-file comparison, another where tests 
themselves should report results.
The automation should check for images as well. All systems should 
exhibit the same result format.
Should be traceable.

Discussed GL#5 - Preparation of Test Materials before Publishing.
- This could interfere with OpsGL (talks about soliciting materials)
- Define a concrete Review Process, where every test is approved and 
status reported.
- A review status should be associated with each test
- Test materials - should have a test plan,publication, test results 
should talk about errata.
- Document the test materials
- Packaging the tests. Process should be clear
- Tar/Zip file should be sufficient to meet the guidelines
- Integration Testing - Testing individual components
- Feedback Mechanism should be established -
- Provide a mechanism for publishing periodic updates of the testsuite.

Discuss GL#6 - Reporting Test Results
(to be continued in the next meeting)

4) Adjourn

Vanitha Venkatraman
Sun Microsystems Inc.
Java Conformance Testing and Tools Group
Santa Clara, CA 95054
Received on Wednesday, 15 October 2003 17:02:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:34 UTC