Orchestrating automation tests for Continuous testing
summary
Claims that Continuous Integration/Delivery only works with a fourth C—Continuous Testing—and shows concrete fixes: build ephemeral environments as code (Terraform/Ansible), treat flaky tests by root‑cause rather than blind reruns, and distribute execution with scalable grids or cloud runners. Examples include 1400 tests that outgrow local runners, using Selenium Grid (historically brittle until Selenium 4 observability), Docker/Kubernetes and Testcontainers for on‑demand environments, and trying LambdaTest HyperExecute as a hosted orchestration option.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:49Continuous delivery vs deployment
- 3:14Continuous testing culture
- 6:01Key elements for success
- 7:47Challenges in testing
- 12:20Path to production strategy
- 13:23Orchestrating automated tests
- 16:38Infrastructure as code
- 17:43Integration testing with containers
- 18:45Quality mindset habits
- 19:27Q&A
related talks
34mWhy continuous testing is essential
32mBetter Continuous Testing in DevOps
01h 00mAutomation Engineer’s Way to Continuous Integration
42mTesting in a Continuous Delivery World
15mTransforming Testing: The Power of TestOps
44mStrategy for Acing Continuous Testing in DevOps
16mStrategy for Acing Continuous Testing
17mContinuous Testing at Scale