Testing in Frontend World
summary
Argues for a concrete frontend testing pyramid and shows what to run where: start with linting (ESLint auto-fix), then fast unit tests (Mocha/Jest), then component testing with Storybook plus snapshot tests and Enzyme for interaction, visual checks with Gemini/WebdriverIO and full E2E via Protractor or webdriver-based suites. Gives concrete numbers (three tests run in ~150ms, thousands slow CI), demonstrates Storybook stories and snapshot failures, and stresses CI integration (Travis/GitLab/Jenkins) for repeatable runs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:47Why frontend testing
- 4:53Frontend testing types
- 6:20New testing pyramid
- 8:29Testing structure and principles
- 9:54FIRST principles for unit tests
- 13:48Test writing theory
- 14:11Linting as first step
- 17:07Unit testing specifics
- 18:51Component testing with React
- 21:20Storybook for visual tests
- 23:06Component interaction testing
- 25:14Visual testing with screenshots
- 26:59Integration testing in frontend
- 28:47Final testing pyramid
- 31:20Q&A
related talks
26mModern Testing Practices in Frontend Applications
50mFrontend-as-a-Service Automated Testing: Layers and CI Pipelines
38mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
49mFrontend Testing: Mapping Out the Territory
32mMake backend devs jealous of your test suite
49mFail Fast Approach in Frontend Development
26mImplementing a test suite in an existing Frontend application
