Software Devs in Test Automation - Dream or Reality in Agile Software Dev?
summary
Product team trains software developers to write e2e tests, picks Cypress after PoCs, and automates the 35 most valuable cases out of 65 using the Graham model; automation lives in CI with smoke and nightly pipelines. Over 10 months manual regression effort falls from 48% to 15%, deployment frequency rises from twice per month to once a week, and cycle time for change drops from 20 days to 7 days. Developer-led test automation achieves measurable sprint-ready outcomes.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:21Welcome
- 0:55About Blerina
- 5:52Product Team
- 6:40Our Vision
- 7:27The System
- 9:26Agile vs Traditional
- 13:08Why Test Automation
- 16:20Software Devs
- 19:05Developer vs Tester
- 21:18UpGrading in Tester Perspective
- 23:16Test Strategy
- 24:40kipling method
- 28:00graham model
- 30:07application description
- 35:46tools
- 37:58cyprus
- 39:08cyprus features
- 42:04Continuous Testing
- 42:37Reporting and Monitoring
- 43:24Results
- 44:46Final Thoughts
related talks
18mEffective Test Automation Framework Design
44mTest Automation as a Development Team
27mTest Effective Development - End 2 (What) End?
21mThe Essential Pillars of Automation Testing for Success
32mWhy testing is a developer's problem
19mBusiness Impact Delivery Using Test Automation
35mSleeping better at night
01h 08mTest Automation Monsters