Full-Stack Test Automation
summary
Argues that shifting checks into unit, integration and contract layers cuts flaky end‑to‑end load and maintenance: migrated one page from AngularJS to Angular with ~20 test cases and implements most as unit/integration/contract tests so there are only 1–2 UI end‑to‑end tests left; injects test IDs for stable locators, runs automation on PRs before manual testing, and reports measurable wins — fewer flaky runs, lower automation cost, faster feedback.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:50Problems with Test Automation
- 2:46Unit Testing
- 4:15Code Coverage
- 5:14Integration Tests
- 6:07Mocking
- 8:39Unit Integration Test
- 11:38API Engine Testing
- 14:41Test Automation Efficiency
- 17:53Continuously Improve
- 20:43Investigate Code
- 30:31Solutions
- 36:03Efficiency Improvement
- 40:47Questions
related talks
51mRedefining test automation
36mFull-stack Testing in is the New Normal
53mModern Web Testing: Going Beyond Selenium
18mEffective Test Automation Framework Design
29mEnd to End Test Automation for Both Horizontal and Vertical Scale
21mThe Essential Pillars of Automation Testing for Success
40mThe Test Automation Firehose
30mModern Web Testing: Going Beyond Selenium