Testing Front-End Applications
summary
Claim: front-end suites with more than 3000 tests become slow and brittle when tests target internals, so tests instead focus on user-visible behavior and integration across components. Uses React examples, replaces Enzyme shallow rendering because enzyme shallow rendering breaks on refactor, mounts real stores (reducers/epics) rather than mocking, and wraps common interactions in small helpers to remove boilerplate. Recommends TDD and libraries like react-testing-library / DOM Testing Library to keep tests stable and meaningful.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 3:40Why tests matter
- 7:55Test smells and pitfalls
- 10:52TDD and test design
- 13:23Team's journey to better tests
- 21:44Lessons learned and improvements
- 25:47Alternative testing tools
- 28:40Summary and best practices
related talks
24mUsing React Testing Library to Write Stronger Tests
45mThe (Dis)Love of Web Testing
53mTesting React Applications
18mTesting React in a Right Way
22mElizabeth Funk - An Introduction to React Testing Library
29mTesting Is All About Principles
10mTesting React Applications
32mEstablishing testing patterns with software design principles
