Fail Fast Approach in Frontend Development
summary
Describes a Frontend "fail fast" testing pipeline that shifts tests left to catch bugs before production by running parallel Jenkins jobs that produce Allure reports and visual regression tests (pixelmatch) with artifacts stored via Git LFS. The testing stack combines unit tests, Storybook, Jest/Enzyme and TypeScript; initial automation setup costs 2 hours to a week with device-job runs ~1 hour weekly and an empirical break-even around nine iterations, leading to fewer manual checks, less cross-team bug ping‑pong and faster feedback.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:31Fail fast approach
- 5:08Classic testing problems
- 6:14Fail fast in teams
- 9:06Four fail fast testing aspects
- 11:13Company tools and stack
- 15:49Optimizing test pyramid
- 21:55Device testing automation
- 27:57Automation vs manual
- 31:52Fail fast results
- 33:16Q&A: Device testing
- 35:24Q&A: Developer load
- 38:41Q&A: Test necessity proof
- 41:11Q&A: Transition time
- 43:03Q&A: Process integration
- 45:52Q&A: Visual test choices
- 48:24Q&A: Dev time impact
- 49:07Summary
related talks
35mTesting in Frontend World
50mFrontend-as-a-Service Automated Testing: Layers and CI Pipelines
26mModern Testing Practices in Frontend Applications
26mImplementing a test suite in an existing Frontend application
41mFrom 0 to 100: How We Jump-Started Our Frontend Testing
34mHow to build front-end web apps that scale
42mWait, I have to test the front end too?
38mFrontend Tests: what nobody said to you