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. Coping With The Broken Web Rodney Rehm - @rodneyrehm

  2. Where I come from

  3. http://medialize.github.io/URI.js/

  4. http://coding.smashingmagazine.com/2012/10/09/designing-javascript-apis-usability/

  5. I like making stuff simple

  6. … recently at work

  7. None
  8. But…

  9. None
  10. What do you mean by „broken“?

  11. None
  12. None
  13. None
  14. None
  15. <select> … been around for ages

  16. Events triggered when clicking on <select> http://rodneyrehm.github.io/select-events/

  17. None
  18. None
  19. Assumptions… http://www.freefoto.com/preview/41-23-4/American-highway-road

  20. … Reality http://farm9.staticflickr.com/8019/7597671400_9dcf23ab7a_o_d.jpg

  21. Check your assumptions. In fact, check your assumptions at the

    door. Lois McMaster Bujold
  22. Despair? Opportunity!

  23. http://www.flickr.com/photos/mennonitechurchusa-archives/7597671400/in/set-72157630434425392

  24. Grokking Results

  25. Single result set

  26. None
  27. Aggregate results

  28. Beware of the flood

  29. Summary and details

  30. Tools?

  31. Running Tests

  32. Running tests

  33. Running tests

  34. Running tests

  35. None
  36. None
  37. None
  38. None
  39. None
  40. https://github.com/rodneyrehm/testharness-helper

  41. None
  42. Aggregating Results?

  43. Storing results

  44. Storing results

  45. Test Environment?

  46. (some) real devices!

  47. (some) real devices!

  48. virtual machines

  49. virtual machines s

  50. Which Browser Is This?

  51. github.com/bestiejs/platform.js Identifying browsers

  52. Utilities?

  53. None
  54. Central System?

  55. CSS WG HTML WG

  56. None
  57. 64 % 24 % 11 % Approved In Review Unknown

  58. Submitted in January

  59. No Fun

  60. Future?

  61. None
  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
  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
  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
  65. None
  66. None
  67. None
  68. They‘re working on it!

  69. Motivation?

  70. your tests are run by W3C and browser vendors

  71. collected data === articles, workshops, talks === street-cred

  72. insights into specifications & credibility for mailing lists

  73. You are part of the web, start caring for it!

  74. When the web is not doing what you want it

    to, fight back, WRITE TESTS! Me, I think
  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
  76. None
  77. Thank You! Questions?

  78. TestTheWebForward.org Join the Rebellion™