Implementing a test suite in an existing Frontend application
summary
Legacy frontend with ~40,000 LOC, ~290 JS files and ~240 React components gets a test runner and CI hooks, keeps existing Selenium end‑to‑end suite but speeds it from ~2 hours to ~20 minutes, adds code formatter and linter, extracts shared UI into a component library, writes characterization tests before refactor, uses error tracking, enforces tests in the definition of done, and raises unit/integration coverage from 0% to ~30% in six months — practical, measurable results.
AI-written summary · about
chapters (7)
- 0:00Intro
- 1:57Background
- 5:03What is the solution
- 7:22Selling the solution
- 13:22Planning
- 15:20Testing
- 22:39Was it worth it
related talks
35mTesting in Frontend World
32mMake backend devs jealous of your test suite
30mTesting Front-End Applications
50mFrontend-as-a-Service Automated Testing: Layers and CI Pipelines
37mTest Automation: From Zero To Hero
08mAdaptation of the E2E Tests for a Big Project
45mTesting the web without testers — success or failure
49mFail Fast Approach in Frontend Development