What?

• Publish test suites for our specs
• A Test suite is composed of test cases
• A Test case exercises one (or more) conformance requirement of the spec (…MUST…)

Why?

• Required to reach Recommendation status
• Necessary to ensure interoperability
• Only way to assess our specs make actual sense

When?

• Required by end of Candidate Recommendation
• Best to start when spec stabilizes
• Trade-off between doing it early and having to update tests often

Who?

• Anyone in and outside of the group
• Great way to discover the spec in depth
• Can actually be fun :)
• Having a test facilitator per spec helps

How?

• Using testharness.js
• Repository per spec in dvcs.w3.org
• Submission/review process to be discussed

Process

• Could be: submit, review, approve
• Or: submit → approved until proved wrong
• If the former, need to agree on more detailed process

Example for getUserMedia test

Walk-through

WebRTC specificities

• Hardware dependent
• Need two browsers
• Specific server-side components
• Protocols vs APIs