Frontend-as-a-Service Automated Testing: Layers and CI Pipelines
summary
An architecture for frontend automated testing that combines Storybook and Jest for isolated component/unit checks with a Protractor+Puppeteer hybrid (including request interception and mocking) for integration and UI flows. The setup supports about 200–300 components across 8–10 projects maintained by five automation engineers, runs regressions twice weekly, and uses a selective CI pipeline that runs tests only for changed components to improve stability and release speed.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 7:56Frontend testing challenges
- 10:59Testing layers
- 14:35Dumb vs smart components
- 19:32Unit testing components
- 23:34Event handling checks
- 26:32Выбор инструментов для E2E-тестирования
- 29:52Playwright and Cypress
- 34:41CI/CD pipelines
- 37:12Contract testing
- 41:53Cross-browser testing
- 45:14Q&A
related talks
35mTesting in Frontend World
49mFail Fast Approach in Frontend Development
28mUsing CI to Test the Frontend: the TeamCity Example
26mImplementing a test suite in an existing Frontend application
41mFrom 0 to 100: How We Jump-Started Our Frontend Testing
18mEffective Test Automation Framework Design
26mModern Testing Practices in Frontend Applications
32mCrafting a Bulletproof testing pipeline for React Apps