Strategy for Acing Continuous Testing in DevOps
summary
Defines continuous testing as automate highest-value tests rather than chasing percent metrics, recommends matching frameworks to personas (Selenium, Cypress, Espresso, XCUITest, Flutter, PWAs, APKs) and running parallel testing in the cloud (Perfecto) to scale. Gives concrete targets: seven concurrent PRs a day with a 10 minute PR window, nightly regressions ~8 hours, and 90–99% stability. Advises immediate removal or quarantine of recurring flaky failures after two occurrences, keep CI green, and measure cost of flakiness (minutes and dollars lost).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:18Digital disruptions
- 5:08AI and machine learning
- 7:46Continuous testing
- 8:50What is continuous testing
- 11:30Pipeline diagram
- 12:46Shift left for
- 18:28automation
- 19:54mobile
- 21:40power testing
- 22:42open and integrated
- 23:35build your testing pipeline
- 24:44phased coverage approach
- 26:22outdated coverage
- 27:23CI pipeline
- 29:20Losing money
- 30:14Troubleshooting
- 32:38Measures
- 35:12QA
- 37:05Questions
- 39:25Perfecto
related talks
16mStrategy for Acing Continuous Testing
32mBetter Continuous Testing in DevOps
34mWhy continuous testing is essential
20mThe Road to Continuous Testing
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
16mWhy is Continuous Testing Important?
44mContinuous Performance Testing in DevOps
30mBest Practices for Accelerating Continuous Testing