Testing Big in JavaScript
summary
Claim: a new test stack called BigTest targets component-driven apps, composes interactors for reliable, chainable DOM actions, and uses Mirage to mock a full client-side API so each test gets fresh, controllable data. Demos use a TodoMVC and a production app with ~1,100 UI tests running ~6 minutes on CI and 96% coverage; tests run in Chrome, Firefox, iOS Safari and more, plug into Mocha, and report very fast, low-flakiness results.
AI-written summary Β· about
chapters (20)
- 0:00Start
- 1:17Unit tests?
- 1:53Render the full application in the browser
- 2:48What are the benefits?
- 3:11Test the loop between the browser & the application
- 4:29Flakey tests
- 5:03Protractor
- 6:33Faster rendering
- 8:02Chainable interactions
- 8:22Take advantage of modern tooling
- 8:51Maintainability & scaleability
- 9:15Full control over the network
- 10:04Cross browser
- 11:03Cross framework
- 11:13Cross test framework
- 11:37Built with components in mind
- 19:08You don't have to wait for the *ability to interact
- 26:41Mirage creates a client side server that mimics your API
- 27:08Shout out @samselikoff for building mirage
- 33:32Create default data with a scenario
related talks
26mModern Testing Practices in Frontend Applications
37mFront-end Testing for Skeptics
27mAutomated Testing for the Modern Web
15mComponent Testing in 2026: The Return of the Browser
55mModern Web Testing: Going Beyond Selenium
27mFullstack testing
09mElemental Testing My Dear Watson - Unit Tests for UI Components
30mTesting Front-End Applications