Cross browser unit testing JavaScript
summary
Claims that running JS unit tests across browsers replaces most slow Selenium runs and gives better coverage: only 72% coverage of JS was exercised by functional tests leaving ~18% untested, Selenium tests average ~8s each while the JS suite runs in 11s total with tests under 1.1s each. Describes using Karma + Istanbul for coverage and an open‑source karma webdriver launcher that plugs Karma into Selenium Grid so unit tests run in real remote browsers and CI without changing browser infrastructure.
AI-written summary · about
chapters (9)
- 0:00The problem with browser testing
- 3:05Benefits of JS unit testing
- 6:12Qualifying test strategies
- 8:35Introducing Karma
- 11:32Installing and configuring Karma
- 15:40Creating and running tests
- 20:09Integrating with Selenium Grid
- 24:53Advanced configuration
- 31:33Summary and Q&A
related talks
38mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
36mModern Web Testing: Going Beyond Selenium
30mModern Web Testing: Going Beyond Selenium
55mModern Web Testing: Going Beyond Selenium
40mTesting Javascript with Jasmine
54mJavaScript Tests in Node, the Browser, and CI
37mFront-end Testing for Skeptics
