Coping With The Broken Web

Coping With The Broken Web

A talk on testing browsers

http://2013.frontendconf.ch/

1fe89044eef1cf027c146e8d7969d8ee?s=128

Rodney Rehm

August 29, 2013
Tweet

Transcript

  1. 7.
  2. 8.
  3. 9.
  4. 11.
  5. 12.
  6. 13.
  7. 14.
  8. 17.
  9. 18.
  10. 26.
  11. 30.
  12. 35.
  13. 36.
  14. 37.
  15. 38.
  16. 39.
  17. 41.
  18. 53.
  19. 56.
  20. 59.
  21. 60.
  22. 61.
  23. 62.

    • identify and fix legal issues (who owns tests) •

    moving to github in progress • extract meta data from specifications for test coverage analysis and linking
  24. 63.

    • centralize test efforts across WGs • run tests in

    cloud and collect data • to build compatibility tables • show browser support in specifications, WebPlatform.org, anywhere
  25. 64.

    • use github for reviewing test suites • integrate adding

    tests into WebPlatform.org • make submitting bugs off a test dead simple • painless local development environment
  26. 65.
  27. 66.
  28. 67.
  29. 74.

    When the web is not doing what you want it

    to, fight back, WRITE TESTS! Me, I think
  30. 75.

    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
  31. 76.