Full-Stack Testing Ethos For a Progressive Team
summary
Argues that full-stack testing means owning all layers of the app — unit, integration, end-to-end and acceptance — and not just broader skill sets; leadership funds proof-of-concepts and appoints masters of one to teach the team; teams require production-like environments and realistic timeboxed goals; integration tests explicitly cover performance, security and service/database issues, while acceptance includes speed and safety; outcome is earlier bug discovery, fewer late-stage fixes and predictable delivery, with risks around time management and unclear handoffs.
AI-written summary · about
chapters (8)
related talks
36mFull-stack Testing in is the New Normal
47mFull-Stack Test Automation
33mAgile Software Testing
25mTesting Processes, One Size Does Not Fit All
20mEffective Testing Approaches for your Application with Cecelia Martinez
45mBe Fullstack, because everyone should
08mFull Stack Developers: Myth or Reality
45mEnd-to-End Test Architectures, a Dead End Road