Upgrade to Pro — share decks privately, control downloads, hide ads and more …

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

  2. Why Me?

  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. thewebevolved.com/support/animation/properties/

  31. Tools?

  32. Running Tests

  33. Running tests

  34. Running tests

  35. Running tests

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

  42. None
  43. Aggregating Results?

  44. Storing results

  45. Storing results

  46. Test Environment?

  47. (some) real devices!

  48. (some) real devices!

  49. virtual machines

  50. virtual machines s

  51. Which Browser Is This?

  52. github.com/bestiejs/platform.js Identifying browsers github.com/tobie/ua-parser

  53. Utilities?

  54. None
  55. Central System?

  56. CSS WG HTML WG

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

  59. Submitted in January

  60. No Fun

  61. Future?

  62. None
  63. None
  64. None
  65. None
  66. Think of it as a guided, collaborative combination of caniuse.com

    quirksmode.org all those independet support tables
  67. None
  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
  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
  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
  71. None
  72. None
  73. They‘re working on it!

  74. Motivation?

  75. your tests are run by W3C and browser vendors

  76. collected data === articles, workshops, talks

  77. insights into specifications & credibility for mailing lists

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

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

    to, fight back, WRITE TESTS! Me, I think
  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!
  81. None
  82. Thank You! Sadly no Q&A, grab me during breaks

  83. TestTheWebForward.org Join the Rebellion™