Building a successful test automation architecture in a microservices environment
summary
Explains concrete practices: run unit and service tests first, limit GUI/Journey tests to critical paths under 10 minutes, use consumer-driven contract tests (Pact) to catch breaking provider changes, run isolated services as a Docker image with test doubles (Mount Bank) and parallel per-test data creation/deletion, automate deployment with blue‑green or canary releases, measure performance with Gatling and scan security with ZAP and dependency‑check, and treat infrastructure as code so automated pipelines actually work.
AI-written summary · about
chapters (25)
- 0:00Introduction and approach
- 2:08Testing topics overview
- 3:43The test automation pyramid
- 11:48Defining service tests
- 12:59Contract and journey tests
- 14:30Independent deployment
- 15:32Using test doubles
- 17:21Isolated test execution
- 18:18Service communication testing
- 18:59Contract testing with Pact
- 21:47Automation and deployment
- 22:47Path to production
- 26:20Infrastructure as code
- 27:39Managing data in testing
- 28:34Parallel data management
- 30:33Cross-functional testing
- 31:16Performance testing
- 32:35Security testing automation
- 33:41Collaborative testing
- 34:19Effective journey tests
- 34:36Production testing
- 36:19Quality analyst mindset
- 39:19Avoiding common traps
- 41:24Recommended reading
- 41:59Q&A and conclusion
related talks
57mEnd-to-End Automated Testing in a Microservices Architecture
18mEffective Test Automation Framework Design
57mBuilding Systems that are #neverdone
35mTest automation guide: How to move away from chain tests
38mScaling Automated Testing & Architecture from Startup to Enterprise
02h 36mTesting Java Microservice
47mBreak Up the Monolith: Testing Microservices
13mStrategies for Application Testing at Scale in Enterprise