Frontend Testing: Mapping Out the Territory
summary
A practical map of front-end testing that claims confidence comes from using the right tool at each level: Cypress end-to-end for user flows and occasional visual checks, Applitools visual grid for cross‑browser visual regressions, JSDOM for fast integration tests that run under Node, and Mocha for narrow unit logic. Recommends many integration tests (the “diamond/trophy” shape), sparse E2E, unit tests for combinatoric logic, and production smoke visual checks after each deploy.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06Why test frontend code
- 8:49Types of frontend tests
- 9:53End-to-end testing demo
- 14:57Visual testing importance
- 21:40Visual regression testing demo
- 27:41Why not only end-to-end tests
- 29:45Integration testing with jsdom
- 33:01Component testing overview
- 35:07Unit testing fundamentals
- 37:33Testing pyramid vs trophy
- 41:46Production testing strategy
- 42:28Summary and final thoughts
- 43:34Q&A session
related talks
35mTesting in Frontend World
38mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
26mModern Testing Practices in Frontend Applications
16mAnatomy of a Test, or the Usefulness of a Frontend Test
38mFrontend Tests: what nobody said to you
32mCypress.io – the State of the Art End-to-end Testing Tool
55mModern Web Testing: Going Beyond Selenium