Shifting Left: How to Build a Culture of Testing
summary
Four-step roadmap: start with research to map stakeholders, decision makers and metrics like false failures, reopen tickets, long test runs and release delays; get buy‑in by aligning changes to those priorities and showing a proof of concept (Cypress + Cucumber in GitLab pipelines with mock service data and visible Jira test widgets); educate via lunch-and-learns, pair/mob programming and central docs; execute with agreed definition of ready and definition of done, track flaky-test reduction, faster runs, and incremental wins via CI/CD and tooling (NX, GitHub Actions, custom Cypress plugins).
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:47Researching your testing culture
- 8:42Getting stakeholder buy-in
- 16:07Educating teams effectively
- 22:46Executing the shift left plan
- 35:13Q&A and closing
related talks
20mThe Road to Continuous Testing
40mEmbracing Shift-Left Testing
44mAchieving Excellence: The Path to an Impactful Test Suite
43mTransformative Culture
20mPanel Discussion on Testing
36mPut Your TestOps Shoes on! Improving Quality by Process Automation
42mImproving Testing Quality by Changing Culture
58mTesting Strategy - New Model, Better Outcomes