• identify and fix legal issues (who owns
tests)
• moving to github in progress
• extract meta data from specifications for
test coverage analysis and linking
Slide 63
Slide 63 text
• centralize test efforts across WGs
• run tests in cloud and collect data
• to build compatibility tables
• show browser support in
specifications, WebPlatform.org, anywhere
Slide 64
Slide 64 text
• use github for reviewing test suites
• integrate adding tests into
WebPlatform.org
• make submitting bugs off a test dead
simple
• painless local development
environment
Slide 65
Slide 65 text
No content
Slide 66
Slide 66 text
No content
Slide 67
Slide 67 text
No content
Slide 68
Slide 68 text
They‘re working on it!
Slide 69
Slide 69 text
Motivation?
Slide 70
Slide 70 text
your tests are run by
W3C and browser vendors
Slide 71
Slide 71 text
collected data
===
articles, workshops,
talks
===
street-cred
Slide 72
Slide 72 text
insights into
specifications
&
credibility for
mailing lists
Slide 73
Slide 73 text
You are part of the
web, start caring for it!
Slide 74
Slide 74 text
When the web is
not doing what you
want it to, fight back,
WRITE TESTS!
Me, I think
Slide 75
Slide 75 text
Recap
• testharness.js to run tests
• firebase.io to aggregate data
• real browsers, devices and BrowserStack
• don‘t wait for W3C to get their testing
sorted, have some fun now