Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Contract Testing - bye-bye Testing Monolith?
Ähnlich wie Contract Testing - bye-bye Testing Monolith? (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Contract Testing - bye-bye Testing Monolith?
- 2. W H AT TO E X P E C T ? No code No tools How it can help you Some practices Source: wallpaper21.com
- 3. A B O U T M E Maarten Groeneweg Portbase Tester & Guild lead @LazyTesting
- 6. MONOLITH PIPELINE App E2E Tests Feature team 1 Feature team 2 Platform team Production
- 7. E2E Tests App App App App App App App App App Feature team 1 Feature team 2 Platform team MICROSERVICE PIPELINE Production
- 8. A REAL MICROSERVICE PIPELINE App Tests App App App App App Tests Tests Tests Tests Tests Feature team 1 Feature team 2 Platform team Production
- 9. REAL MICROSERVICES IN PRODUCTION App App App App App App App App App Source: wikia.com
- 11. THE SOLUTION
- 12. C O N T R A C T T E S T I N G Kills integration bugs Does not harm your microservices Enables autonomous delivery Source: therange.co.uk
- 13. STEP 1: CREATE CONTRACT All-the- beers-app Beers API /beers Consumer Provider Contract When: GET /beers Then: [{ name: 'Kaapse Harrie', brewery: 'Kaapse Brouwers'}]
- 14. STEP 2: TEST CONSUMER AGAINST MOCK Contract Beer API Mock All-the- beers-app Test Consumer
- 15. STEP 3: VALIDATE CONTRACT Contract Contract Contract Beers API Provider When: GET /beers Then: [{ name: 'Kaapse Harrie', brewery: 'Kaapse Brouwers'}]
- 16. MICROSERVICES PIPELINE TestsConsumer Provider Tests Consumer tests Provider Mock Contract Ok Provider tests Production Production
- 17. A DVA N TA G E S Autonomous testing Consumer driven contracts Enables provider to optimize Insight in usage Source: techtimes.com
- 18. 7 ANTI- PATTERNS
- 21. #3: HAPPY PATH COVERAGE Source: reddit.com
- 26. CONCLUSION
- 27. I T ' S A W E S O M E Autonomous releasing No testing monolith Insight in integrations But don't forget the humans Source: Futurama
- 28. M O R E I N F O lazytesting.com/contract- testing @LazyTesting
Hinweis der Redaktion
- Ask questions
- Test Automation Human aspect We use pact
- Slow feedback E2E test have knowledge of everything Dependencies between teams (if team 1 introduces a bug, others cannot deploy) Other team needs to provide it’s application => need for 1 or more integrated envs
- This is what you want
- A lot of implicit expectations
- How I feel as tester> slackline Creating a monolith Having integration bugs
- Next slide> talk about beer
- 1. Consumer writes a contract
- 2. Consumer can mock provider based on the contract 3. Consumer can test it’s own app against the mock But still… not that useful (just mocking)
- 4. Provider can validate the contract(s) against the actual implementation (and the other way around)
- Explain provider/consumer broker
- Consumer dictated contracts Customer collaboration over contract negotiation
- Tools over human interaction
- Bad coverage - forgetting fault paths (404s) Asume an evil provider team
- Consumers expect more then they actually need Example : all the beers api doesn’t need a breweyname
- Autonomous teams, what if 1 team doesn’t wat to?
- Integration testing is complex, accept it (your e2e test are complex as well) Complexity in testing is a smell of complexity in architecture
- Pipelines of provider and consumer need to interact If release provider: check all contracts If release of consumer: validate contract against provider