Creating a QA/DEV Collaborative Testing Strategy
summary
Pipeline work moves release decisions from people into automation so pipeline decisions run in Jenkins jobs and flag green or red; a new role called a test architect joins developers to write test recipes—brief, layered scenario lists that decide whether to test at unit component API or end-to-end levels. The method is piloted at enterprises of 500–50,000 staff and pairs dev and test work to shorten feedback loops, remove duplication and follow a one-to-five rule for test levels.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:33Repeating testing challenges
- 4:00Traditional QA failures
- 8:19Pipeline-based organizations
- 15:31Skills for pipeline orgs
- 22:41Pipeline testing value
- 26:16Test architect role
- 28:47Test recipes explained
- 35:00Test recipe benefits
- 41:45Deciding test levels
- 49:35Summary
- 50:40Resources
related talks
44mQA in a Pipeline Based Organization
30mQA in DevOps: Transformation thru Automation via Jenkins
53mIs having a QA a symptom of a dysfunctional team?
06mDoes QA have a place in DevOps? Heck yeah!
27mExploring a DevOps Transformation Like a Tester
30mCollaboration Between the Dev and the Test Team
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
47mHow Testing is Evolving in DevOps