Frontend testing for Wix viewer, case study
summary
Describes concrete test choices, tradeoffs and results: why unit tests in Node/JSDOM mask integration bugs, how state-machine unit tests isolate logic, how puppeteer headless Chrome becomes the primary integration tool, when Selenium or Karma still matter, and how visual regression switches from image diffs to rectangle-based visual checks. Gives numbers (puppeteer 80–90% offline tests), specific failures encountered, and what actually worked in the Wix viewer pipeline.
AI-written summary · about
chapters (4)
- 0:00Start
- 20:36Browser Unit Test Karma, Jasmine
- 21:40Integration Tests Puppeteer, JEST
- 25:39State Unit Test Split your state code from components
related talks
09mElemental Testing My Dear Watson - Unit Tests for UI Components
15mComponent Testing in 2026: The Return of the Browser
01h 02mModern web testing and automation with Puppeteer
29mState of Web Integration Testing
28mFrontend Testing
27mVisual UI Testing – Testing the Last Mile
38mModern Web Testing: Going Beyond Selenium
19mWorking Well: The Future of Web Testing