Coping With The Broken Web

A talk on testing browsers

http://2013.front-trends.com/

Transcript

1. Coping With The Broken Web Rodney Rehm - @rodneyrehm
2. Where I come from
5. I like making stuff simple
6. …at work
8. But…
10. What do you mean by „broken“?
21. <select> … been around for ages
22. Events triggered when clicking on <select>
23. Assumptions… http://www.freefoto.com/preview/41-23-4/American-highway-road
24. … Reality http://farm9.staticflickr.com/8019/7597671400_9dcf23ab7a_o_d.jpg
25. Check your assumptions. In fact, check your assumptions at the door. Lois McMaster Bujold
26. Despair? Opportunity!
27. http://www.flickr.com/photos/mennonitechurchusa-archives/7597671400/in/set-72157630434425392
28. What do we need?
29. Single result set
30. Aggregate results
31. Beware of the flood
32. Summary and details
33. Tools?
34. Running tests
35. Running tests
36. Storing results
37. Storing results
38. Test environment
39. Test environment
40. github.com/bestiejs/platform.js Identifying browsers
42. Central System?
43. CSS WG HTML WG
45. 64 % 24 % 11 % Approved In Review Unknown
46. Submitted in January
47. No Fun
48. Future?
52. They‘re working on it!
53. Motivation?
54. test suites are run by W3C and browser vendors
55. collected data equals articles, workshops, talks
56. YOU are the web, act like it!
57. Recap • testharness.js to run tests • firebase.io to aggregate data • real browsers / devices or BrowserStack • don‘t wait for W3C to get their testing sorted, have some fun now
59. Thank You! Questions?