RE: HTML Testing Task Force Conf Call Agenda 2/26/2013

Notes

The group discussed how to leverage robins coverage report such that we start to enumerate sections of the spec that we should prioritize for testing.
We agreed that that the task force should start to classify every section in the spec, such that each section would be labeled.

For example...
    A) no requirements
    B) has conformance requirements, no tests, known interop issues (for example the-input-byte-stream)
    C) has conformance requirements, has tests (canvas)
    D) has conf reqs, no tests, no known interop issues

http://w3c-test.org/html-testsuite/master/tools/coverage/

IRC -> http://www.w3.org/2013/02/26-htmlt-irc

From: Kris Krueger [mailto:krisk@microsoft.com] 
Sent: Monday, February 25, 2013 9:24 PM
To: 'public-html-testsuite@w3.org'
Subject: HTML Testing Task Force Conf Call Agenda 2/26/2013

Agenda

* Marking non-automated tests (meta-data)
* Discuss enumerating areas of the HTML5 spec to focus/suggest testing coverage

-Thanks!

IRC #HTMLT
Time 16:00-17:00 UTC (11:00am-12:00pm Boston local)

Received on Thursday, 28 February 2013 00:40:07 UTC