This document discusses approaches for automating tests for microservices. It recommends automating each microservice separately with unit, integration, component, contract, and end-to-end tests. Unit tests should be implemented by developers and focus on positive and corner cases. Integration tests check how services work with persistence layers and APIs. Component tests exercise the main functionality through public APIs. Contract tests validate the semantics of service interactions without testing functionality. End-to-end tests cover business flows and platform dependencies. The document emphasizes running tests locally and using tools like Docker, WireMock, Pact and Spring Cloud Contract.

1. AUTOMATING MICROSERVICES:
WHAT, WHERE AND WHEN
Oleksandr Romanov
IT Weekend Dnipro 2018

2. WHO AM I?
• 6+ years in test automation
• QA Automation Lead at Playtika

3. DICLAIMER
• All opinions are completely my own
• Microservices – backend architecture
• For hardcore code, check =>

4. The story so far

5. REGRESSION. RELEASE. REPEAT.

6. First automated tests…

9. CROSS BROWSER AUTOMATION

10. TESTS ON IE

13. Good old flakiness

14. MAYBE, API LEVEL TESTING?

15. CHILL OUT, HERO

16. HERE COMES
MICROSERVICES!
WINTER IS
COMING?

17. MICROSERVICES?
WHAT THE HELL ARE

18. API LEVEL TESTING, AGAIN?

19. — YOUR ARCHITECT
«We need to release each microservice separately and fast».

21. THE PYRAMID
https://martinfowler.com/ar
ticles/microservice-testing/

22. MICROSERVICES TEST AUTOMATION APPROACH

23. GUIDE THROUGH THE LEVELS

24. Unit tests
• Implemented by developers
• Concentrated on positive and corner cases
• Mocking and stubbing are heavily used

25. Integration tests: what to test
• Persistence: SQL and NoSQL storages
• Gateway: HTTP REST, Messaging, RPC,
etc.

26. Integration tests: how to test
• In – memory solutions for testing
• Dependencies in docker containers
• Using SQLUnit / NoSQLUnit / scripts for test data

27. Component tests: what
• Testing main functionality
of the microservice
• Testing corner cases if
external services are
unavailable

28. Component tests: how to test
• Testing through public / internal API
• Running service locally and / or dependencies in docker containers
Test Containers: https://bit.ly/2KYhc4N
Spring Boot Test Containers: https://bit.ly/2GTc13S
• Mocking out external services: e.g. via WireMock https://bit.ly/2pSFLZb

29. Contract
tests: what
• Testing semantics
• Do not test functionality

31. Contract tests:
example

32. Contract tests: how
PACT - https://bit.ly/2GUBIAX
Spring Cloud Contract - https://bit.ly/2GYi0Jy

33. End – to – End tests:
• Cover business flows
• Cover platform dependent cases
• Can be done on API or UI levels

34. So, what?

35. One bad
microservice?

37. Recommendations
• Sam Newman – Building Microservices https://oreil.ly/1pp6qmx
• Martin Fowler – Testing Strategies in Microservices
https://bit.ly/2pWi0AA

38. To sum up:
• Automate each microservice separately
• Run locally as much tests as you can
• End - to - end tests are important too

39. Twitter: @al8xr
Skype: alex_roma_nov
THANK YOU!