Selenium at the Speed of Light Turbocharging Your Test Execution
summary
Live demo uses Docker, WebDriver IO, Selenium/ChromeDriver and OpenMCT with TestingBot-sponsored cloud mention and injects latency via Toxyproxy chaos injection. Adding just 500 ms latency to a single component turns a 4s local baseline into a runtime increase of +175%, two injected hops push it to ~21s and force timeouts up by hundreds of percent. Collocating test runner, browser and app and shifting interactions to APIs cuts runtime (example: 27h to 9h) and dramatically reduces flakiness.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:45OpenMCT use case
- 4:15Network performance in UI testing
- 7:05CI architecture limits
- 9:12Toxiproxy for chaos testing
- 11:00Live Selenium demo
- 12:07Latency impact on tests
- 13:31Runtime analysis with interference
- 15:14Latency experiment findings
- 16:16Reducing execution time with Selenium Grid
- 16:59Architecture improvements
- 19:07API-first vs UI testing
- 20:12UI vs API resource costs
- 20:57Future with bidirectional protocols
- 21:40Scaling risks impact
- 22:21Summary
- 22:47Q&A
