Full-stack Testing in is the New Normal
summary
Claims that full‑stack testing catches issues across UI, API, backend and middleware earlier, yields faster feedback and fewer late bugs, and transitions into continuous testing once automation for performance runs in CI. Practical steps: start with a simple story, pick tools that fit the tech stack and workflow, run bi‑weekly cross‑team reviews, and have masters‑of‑one train the team. Tradeoffs: short productivity dip for training, clearer handovers required to avoid responsibility gaps.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:53Full-stack testing is new normal
- 10:16Skills for test engineers
- 13:25Transitioning to full-stack testing
- 20:53Mastery versus versatility
- 24:29Breaking silos for collaboration
- 29:23Full-stack to continuous testing
- 31:07Benefits of full-stack testing
- 33:15Challenges and solutions
- 35:42Start small aim big
related talks
08mFull-Stack Testing Ethos For a Progressive Team
47mFull-Stack Test Automation
13mFewer Tools, More Impact: An Automated Testing Strategy for Scale-Up
20mThe Road to Continuous Testing
26mModern Testing Practices in Frontend Applications
49mThe Whole Team Approach to Testing in Continuous Delivery
34mWhy continuous testing is essential
29mProgressive Testing to Meet the Performance Imperative
