How to ensure Testing Robustness in Continuous Testing Environments
summary
Claims concrete fixes for test smells and shows they work: implement polling with 1s interval up to 7s to handle asynchronous microservices and reduce flakies (example failures drop from six–seven to one), add reusable helper classes to remove duplicated test code, run cleanup hooks to delete created objects after failures, build a machine manager and selenium grid to exercise multiple OS/browser combinations, enable automated Xray reporting via its APIs, push artifacts to S3 and metrics to CloudWatch, and run static analysis in CI.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:22Agenda
- 1:42INTRODUCTION
- 2:23Microservices
- 12:00Retry Algorithms
- 14:41Clean Up
- 15:21Test Groups
- 15:51Test History
- 16:35Execution Coverage
- 17:52Test Input
- 18:47Helper Classes
- 20:55Code Quality
- 21:05Make Use of Tools
related talks
26mHow to ensure Testing Robustness in Microservice
37mBuilding Quality with Foundations of Mud
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
44mStrategy for Acing Continuous Testing in DevOps
17mContinuous Testing at Scale
34mWhy continuous testing is essential
24mOrchestrating automation tests for Continuous testing
32mTest Automation and Beyond: Implementing Continuous Testing Effectively