Coping With The Broken Web

Transcript

1. 1.

   Coping With The Broken Web Rodney Rehm - @rodneyrehm

2. 2.

   Where I come from

3. 3.

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

4. 4.

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

5. 5.

   I like making stuff simple

6. 6.

   … recently at work

7. 7.

   None
8. 8.

   But…

9. 9.

   None
10. 10.

    What do you mean by „broken“?

11. 11.

    None
12. 12.

    None
13. 13.

    None
14. 14.

    None
15. 15.

    <select> … been around for ages

16. 16.

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

17. 17.

    None
18. 18.

    None
19. 19.

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

20. 20.

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

21. 21.

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

    door. Lois McMaster Bujold
22. 22.

    Despair? Opportunity!

23. 23.

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

24. 24.

    Grokking Results

25. 25.

    Single result set

26. 26.

    None
27. 27.

    Aggregate results

28. 28.

    Beware of the flood

29. 29.

    Summary and details

30. 30.

    Tools?

31. 31.

    Running Tests

32. 32.

    Running tests

33. 33.

    Running tests

34. 34.

    Running tests

35. 35.

    None
36. 36.

    None
37. 37.

    None
38. 38.

    None
39. 39.

    None
40. 40.

    https://github.com/rodneyrehm/testharness-helper

41. 41.

    None
42. 42.

    Aggregating Results?

43. 43.

    Storing results

44. 44.

    Storing results

45. 45.

    Test Environment?

46. 46.

    (some) real devices!

47. 47.

    (some) real devices!

48. 48.

    virtual machines

49. 49.

    virtual machines s

50. 50.

    Which Browser Is This?

51. 51.

    github.com/bestiejs/platform.js Identifying browsers

52. 52.

    Utilities?

53. 53.

    None
54. 54.

    Central System?

55. 55.

    CSS WG HTML WG

56. 56.

    None
57. 57.

    64 % 24 % 11 % Approved In Review Unknown

58. 58.

    Submitted in January

59. 59.

    No Fun

60. 60.

    Future?

61. 61.

    None
62. 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. 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. 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. 65.

    None
66. 66.

    None
67. 67.

    None
68. 68.

    They‘re working on it!

69. 69.

    Motivation?

70. 70.

    your tests are run by W3C and browser vendors

71. 71.

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

72. 72.

    insights into specifications & credibility for mailing lists

73. 73.

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

74. 74.

    When the web is not doing what you want it

    to, fight back, WRITE TESTS! Me, I think
75. 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. 76.

    None
77. 77.

    Thank You! Questions?

78. 78.

    TestTheWebForward.org Join the Rebellion™