Why continuous testing is essential
summary
Argues that continuous testing is the enabler for continuous delivery and shows concrete practices: acceptance-test-driven development with Gherkin, unit tests tracked by Sonar, pipelines in Jenkins that run cucumber/appium/calabash suites, and performance driven earlier with jmeter plus New Relic/AppDynamics. Describes built tooling — OneSource test-data API to create conditioned accounts, an open HiGia pipeline dashboard that reveals bottlenecks, and service virtualization stubs to scale performance tests — and cites teams losing ~40–50% capacity and 30–40% defect leakage before these fixes.
AI-written summary · about
chapters (8)
- 0:00Start
- 11:12Solution - Real-time Automation
- 12:50Solution - Open Source Tools
- 13:55Solution - Test Duta
- 15:16Solution - Service Virtualization
- 17:40Solution - Environments
- 24:10Scaling Continuous Testing DIY
- 25:20What does this mean for me?
related talks
32mBetter Continuous Testing in DevOps
16mWhy is Continuous Testing Important?
42mTesting in a Continuous Delivery World
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
24mOrchestrating automation tests for Continuous testing
16mStrategy for Acing Continuous Testing
32mTest Automation and Beyond: Implementing Continuous Testing Effectively
44mStrategy for Acing Continuous Testing in DevOps