Testing in a Service-Based Environment, Staged Acceptance
summary
Testing in service-based systems requires concrete rules and tooling rather than vague advice. The talk covers issues like an ESB (Tibco) that transforms data and exposes Google Maps integration which forces consumers to be tested twice; the team builds test drivers and mocks and evaluates commercial virtual service tools but finds maintenance expensive. To reduce risk and effort they run some integration tests against production, use risk-based selective regression testing, and create formal Generic Test Agreements with partners.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:22Service-oriented architecture
- 8:01Service integration examples
- 13:27Staged acceptance testing
- 17:46Orchestration challenges
- 21:00Testing service chains
- 24:58Integration vs end-to-end
- 29:13Acceptance testing updates
- 34:21Test levels complexity
- 38:21Test manager role
- 40:22Microservices testing
- 43:38Maintaining service updates
- 45:04Q&A
related talks
31mTesting an Enterprise Service Bus: What? Where? How?
19mAutomatic Testing for Services at Scale
45mBuilding a successful test automation architecture in a microservices environment
10mIntegration Testing – a thought experiment
08mTesting Microservices
01h 00mAcceptance Testing Sounds Easy, But Is Hard to Get Right
05mNew Rules Of Engagement For Product Quality: Testing-As-A-Service In ...
57mAdvanced Testing Techniques: Tips from the trenches
