Microservice Test Strategy (@Bonn Code Meetup)
•
0 likes•107 views
Based on a scientific paper by Thoughtworks, this talk will introduce you to a common approach on how to test microservices. We walk through typical components of a microservice and how to test them using different types of tests. Finally we will talk about how to combine these tests so that in the end you can have a very high confidence with your code but still be able to release it within minutes.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Microservice Test Strategy (@Bonn Code Meetup)
Similar to Microservice Test Strategy (@Bonn Code Meetup) (20)
More from Per Bernhardt
More from Per Bernhardt (14)
Recently uploaded
Recently uploaded (20)
Microservice Test Strategy (@Bonn Code Meetup)
- 1. Microservice Test Strategy Per Bernhardt, Staff Software Engineer March 5th 2020
- 3. 3
- 4. 4 • A Typical Service • Types of Tests • Unit Tests • Integration Test • Component Tests • Contract Tests • End-to-End Tests • Combining Tests • Test Pyramide • Be Lean • IMHO • Q & A • Links Agenda
- 6. 6 “Microservices connect with each other over network and make use of external datastores” https://martinfowler.com/articles/microservice-testing/#anatomy-connections
- 9. 9 Unit Tests • Unit Tests should test single/few „classes“ • Mock any external dependency • Should run in „seconds“ • Use your tooling
- 10. • Use xUnit tooling • Use docker where possible • External Services: Test protocol, not behaviour • Should run in „minutes“ 10 Integration Tests
- 11. 11 Component Tests – In-Process • Use xUnit tooling • Mock networking • Use your tooling • Use API to setup fixtures • Should run in „minutes“
- 12. 12 Component Tests – Out-Of-Process • Same but with networking • Tends to be a bit slower
- 13. 13 Contract Tests Contract Testing ensures that a pair of applications will work correctly together by checking each application in isolation to ensure the messages it sends or receives conform to a […] "contract". https://docs.pact.io/
- 15. 15 Contract Tests • defines a contract DSL • can start a HTTP server mock based on a contract • can start a HTTP client mock based on a contract • can share contracts between isolated build pipelines
- 17. 17 Contract Tests Consumer Testing Provider Testing Broker 1. Define contracts based on current implementation 2. Send contracts to broker If we deploy 3. Get contracts from broker and check verification 4. Deploy! Can trigger 1. Load contracts from broker 2. Try to verify contracts 3. Send results to broker Both processes run independently!
- 18. 18 End-to-end Tests • Needs an environment with all participating services • Should have fresh state • Tends to be expensive in maintenance • Tends to be flaky • Tends to be slow • Makes pipelines dependent of each other
- 20. 20 Test Pyramide • Is about test maintainability • Try to test ASAP • Try to DRY • Trust test composition
- 21. 21 Be Lean • Test by user impact • „Don‘t“ test MVPs • Ask your P.O.
- 22. 22 IMHO • Isolate your pipeline • Automate everything • Iterate & improve • Deliver as fast as possible
- 23. 23 Q & A
- 24. 24 Links • https://martinfowler.com/articles/microservice-testing/ • https://de.slideshare.net/perprogramming/communication-in-a-microservice-architecture • https://de.slideshare.net/perprogramming/contract-tests-mit-pact • https://de.slideshare.net/perprogramming/microservice-teststrategie-mit-symfony2