Best Practices for Accelerating Continuous Testing
summary
Seven concrete practices: make tools topology-aware and available as RESTful microservices, orchestrate physical and virtual resources, use self‑healing test infrastructure and credential servers, pipeline and cache tests, stop on hit thresholds, and surface relevant analytics for fast triage. Case data: a network product with 360 developers, 36M LOC, 200 topologies and 12,000 daily test cases gets automated tests to 85%, cuts deploy defects from 1,260 to 10, and halves major release time.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 4:08DevOps
- 5:10Test Environment
- 6:35Getting it wrong has catastrophic results
- 8:26Two key principles
- 9:31Continuous testing is everywhere
- 12:21Continuous testing best practices
- 14:02Quality
- 15:05Culture
- 16:48Structure Process Design
- 18:39Test Ready Tools
- 20:11Integration
- 20:31Topologies
- 21:10Accelerated Testing
- 23:35Relevant Analytics
- 25:06Case Study
- 27:26Best Practices Tool
- 28:21Summary
- 28:49Take aways
- 29:01Spirent Help
related talks
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
34mWhy continuous testing is essential
44mStrategy for Acing Continuous Testing in DevOps
20mThe Road to Continuous Testing
16mStrategy for Acing Continuous Testing
57mOptimizing Your Testing Team
32mTest Automation and Beyond: Implementing Continuous Testing Effectively
24mOrchestrating automation tests for Continuous testing