Building an automated testing suite...
summary
A DIY automated suite that claims to cover 100,000+ combinations actually builds a grammar, an API to enumerate player/media/browser/OS variables, an environment generator that spins test pages, a scheduler hooked into CI and a reporter that captures console logs XHR WebSocket screenshots for human triage. Tests run with Selenium + Jasmine to simulate user actions; desktop coverage works and surfaces flaky false positives, iOS/Android are only half implemented, and the platform reduces manual QA but still needs humans to validate failures.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:26What happens before production
- 9:12What it took
- 12:05Forge
- 13:00Requirements
- 13:30Selenium
- 16:32Complex use cases
- 17:41Selenium on steroids
- 20:08Task report
- 20:56Reporting
related talks
14mDebugging Secrets of a Lazy Developer
45mTesting the web without testers — success or failure
35mBuild an automation framework... with a developer mindset
33mBuilding an Automated Test System from Scratch
41mWriting Well-Abstracted Self-Testing Automation On Top Of Jello-O
34mEnd to end testing a world of web, mobile & desktop apps
42mReliable and Maintainable Webdriver Tests
39mTesting, Testing, 1, 2, NaN