Shift Left Testing for Continuous Collaboration
summary
Argues that moving QA earlier cuts feedback loops from weeks to days by using feature branches and automated or manual checks per branch so each pull request gets its own deployable preview. Demonstrates Probo.ci with Pantheon Multidev and Tugbot.qa style review apps, shows piping Lighthouse audits into the preview, pinning previews for longer review, and using acceptance criteria to catch accessibility and legal issues like the LSAC ADA consent decree. Claims this reduces integration churn and speeds client signoff.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:44Kaizen and Kanban
- 1:45Shift Left Testing
- 14:16Acceptance Testing
- 16:37Pull Request Previews
- 21:27Acceptance Criteria
- 38:48User Acceptance Test
- 46:48Internal Review
related talks
11mTransforming Code Review into a Learning Tool for QA Teams
45mIs there a place for QA in modern agile autonomous fast-flow teams?
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
52mCreating a QA/DEV Collaborative Testing Strategy
40mEmbracing Shift-Left Testing
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
49mThe Whole Team Approach to Testing in Continuous Delivery