Continuous Testing Meets the Classroom at Code.org
2 likes831 views
The document discusses the continuous testing practices implemented by Code.org, particularly focusing on automated testing using tools like Selenium and Cucumber. Key challenges faced include testing across multiple browsers, handling local changes, and managing intermittent test failures, with solutions provided for each issue. Overall, the document emphasizes the importance of building a library of testing steps and the benefits of improving testing speed and efficiency.
Continuous Testing Meets the Classroom at Code.org
- 1. Continuous Testing Meets the Classroom bcjordan.com [email protected] @bcjordan Brian Jordan, software engineer at Code.org
- 2. Code.org
- 3. non-profit
- 5. Hour of Code
- 8. 200 million tried Hour of Code
- 9. now what?
- 12. 20k K-12 teachers trained
- 13. intro courses: 260k teachers 8mil students
- 15. how do you even start automated testing?
- 17. why test? what is Code.org's testing context?
- 18. the context
- 19. the context
- 20. the context
- 21. the context
- 22. the context
- 23. so how do we test all that?
- 24. how we started Selenium testing
- 25. how our tests are organized and run selenium-webdriver cucumber
- 26. takeaways
- 27. Build a library of steps
- 28. Build a library of test levels
- 29. Build a library of annotations @no_mobile @no_ie9 @skip @db_access@as_student
- 33. what challenges did we end up facing?
- 48. what do they look like when running?
- 49. Speed Run!
- 56. justifying tests
- 67. dev of the day
- 68. what's next?
- 69. per-PR tests
- 70. takeaways
- 71. start small
- 72. everybody tests
- 74. Q&A bcjordan.com [email protected] @bcjordan Brian Jordan, software engineer at Code.org code.org/help github.com/code-dot-org