Coping With The Broken Web

1fe89044eef1cf027c146e8d7969d8ee?s=47 Rodney Rehm
October 25, 2013

Coping With The Broken Web

A talk on testing browsers

https://border-none.net/

1fe89044eef1cf027c146e8d7969d8ee?s=128

Rodney Rehm

October 25, 2013
Tweet

Transcript

  1. 2.
  2. 7.
  3. 8.
  4. 9.
  5. 11.
  6. 12.
  7. 13.
  8. 14.
  9. 17.
  10. 18.
  11. 26.
  12. 31.
  13. 36.
  14. 37.
  15. 38.
  16. 39.
  17. 40.
  18. 42.
  19. 54.
  20. 57.
  21. 60.
  22. 61.
  23. 62.
  24. 63.
  25. 64.
  26. 65.
  27. 66.

    Think of it as a guided, collaborative combination of caniuse.com

    quirksmode.org all those independet support tables
  28. 67.
  29. 68.

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

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

    • centralize test efforts across WGs • run tests in

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

    • use github for reviewing test suites • integrate adding

    tests into WebPlatform.org • make submitting bugs off a test dead simple • painless local development environment
  32. 71.
  33. 72.
  34. 79.

    When the web is not doing what you want it

    to, fight back, WRITE TESTS! Me, I think
  35. 80.

    Recap • if you write tests, use the W3C Infrastructure,

    avoid proprietary things • don‘t wait for W3C to get their testing sorted completely, have some fun now* * good for HTML5 APIs already!
  36. 81.