The history and purpose of testing normative changes is explained in the blog post "improving interoperability." Through outreach efforts in 2017 Q2, Q3 and Q4 – and momentum – the hope is that soon testing will be an integral part of virtually all web standards work.
See "from idea to full interop" for how this might fit into the standards lifecycle. The "improving interop with web-platform-tests" talk also covers some of the same ground.
- Pointer Events (commit)
- WHATWG contributor and maintainer guidelines (issue) (14 specs)
- Service Workers (PR)
- Web Performance WG (PR) (12 specs)
- IndexedDB (PR)
- Pointer Lock (PR)
- Payment Request (commit)
- Web Animations (PR)
- WebVTT (PR)
- FX Task Force (PR), covering 6 maintained specs:
- CSSWG (minutes, issue, PR) (32 specs in CR or later + CSSOM + CSSOM View)
- Intersection Observer (commit)
- SVGWG (commit, charter, background) (8 specs)
- Content Security Policy (PR)
- Device APIs Working Group:
- Clipboard API and Events (PR)
- File API (PR)
- Static Range (PR)
- UI Events (PR)
- File and Directory Entries (PR)
- Resize Observer (PR)
- Web Audio API (PR)
- Keyboard Lock (PR)
- WebUSB (PR)
- Feature Policy (PR) (wording tweak, copy from this one)
- Vibration (PR)
- Touch Events (PR)
- Gamepad API (PR)
- WebVR (PR)
- DOM Parsing and Serialization (PR)
- Web MIDI API (PR)
- WebRTC (issue, PR)
- Presentation API (PR)
- Web Application Security WG (PR) (12 specs)
- Houdini TF (PR)
This is ~105 specs.
In https://foolip.github.io/day-to-day/ there are ~210 specs, so we're 50% done!
See "a policy for web-platform-tests coverage is adopted for 40 more specs" in Ecosystem Infra 2017 Q4 OKRs.