Coping With The Broken Web

A talk on testing browsers

https://border-none.net/

Transcript

1. Coping With The
   Broken Web
   Rodney Rehm - @rodneyrehm
   

   View Slide

2. Why Me?
   

   View Slide

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

   View Slide

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

   View Slide

5. I like making stuff
   simple
   

   View Slide

6. … recently at work
   

   View Slide

7. View Slide

8. But…
   

   View Slide

9. View Slide

10. What do you mean by
    „broken“?
    

    View Slide

11. View Slide

12. View Slide

13. View Slide

14. View Slide

15. 
    … been around for ages
    

    View Slide

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

    View Slide

17. View Slide

18. View Slide

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

    View Slide

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

    View Slide

21. Check your
    assumptions. In fact,
    check your assumptions
    at the door.
    Lois McMaster Bujold
    

    View Slide

22. Despair?
    Opportunity!
    

    View Slide

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

    View Slide

24. Grokking Results
    

    View Slide

25. Single result set
    

    View Slide

26. View Slide

27. Aggregate results
    

    View Slide

28. Beware of the flood
    

    View Slide

29. Summary and details
    

    View Slide

30. thewebevolved.com/support/animation/properties/
    

    View Slide

31. Tools?
    

    View Slide

32. Running Tests
    

    View Slide

33. Running tests
    

    View Slide

34. Running tests
    

    View Slide

35. Running tests
    

    View Slide

36. View Slide

37. View Slide

38. View Slide

39. View Slide

40. View Slide

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

    View Slide

42. View Slide

43. Aggregating Results?
    

    View Slide

44. Storing results
    

    View Slide

45. Storing results
    

    View Slide

46. Test Environment?
    

    View Slide

47. (some) real devices!
    

    View Slide

48. (some) real devices!
    

    View Slide

49. virtual machines
    

    View Slide

50. virtual machines
    s
    

    View Slide

51. Which Browser Is This?
    

    View Slide

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

    View Slide

53. Utilities?
    

    View Slide

54. View Slide

55. Central System?
    

    View Slide

56. CSS WG HTML WG
    

    View Slide

57. View Slide

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

    View Slide

59. Submitted in January
    

    View Slide

60. No Fun
    

    View Slide

61. Future?
    

    View Slide

62. View Slide

63. View Slide

64. View Slide

65. View Slide

66. Think of it as a
    guided, collaborative
    combination of
    caniuse.com
    quirksmode.org
    all those independet support tables
    

    View Slide

67. View Slide

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
    

    View Slide

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
    

    View Slide

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
    

    View Slide

71. View Slide

72. View Slide

73. They‘re working on it!
    

    View Slide

74. Motivation?
    

    View Slide

75. your tests are run by
    W3C and browser vendors
    

    View Slide

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

    View Slide

77. insights into
    specifications
    &
    credibility for
    mailing lists
    

    View Slide

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

    View Slide

79. When the web is
    not doing what you
    want it to, fight back,
    WRITE TESTS!
    Me, I think
    

    View Slide

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!
    

    View Slide

81. View Slide

82. Thank You!
    Sadly no Q&A, grab me during breaks
    

    View Slide

83. TestTheWebForward.org
    Join the Rebellion™
    

    View Slide