How to test microservices and stay sane

Microservices shine in many aspects, but testability. Whenever you deploy a service, no matter how small it is, as long as it has dependencies, you have to keep them in mind. By definition, microservices have lots of dependencies and makes you appreciate how easy it is to test integration in a monolithic code base. There is a concept of contract testing that makes testing microservices a breeze. In the presentation, it's shown on an example of Pact, an open source library with adapters for many popular languages.

Transcript

1. How to test microservices
   and stay sane
   Tatiana Shepeleva @ Toptal
   

   View Slide

2. !2
   toptal.com
   

   View Slide

3. What are microservices?
   

   View Slide

4. What are microservices?
   

   View Slide

5. What are microservices?
   • “Lightweight” API
   • Independently releasable
   • Have separate test suites
   

   View Slide

6. What are microservices?
   • “Lightweight” API
   • Independently releasable
   • Have separate test suites (but really?)
   

   View Slide

7. How to know if you can deploy?
   

   View Slide

8. Bored meme!
   

   View Slide

9. View Slide

10. Super end-to-end tests
    

    View Slide

11. View Slide

12. View Slide

13. View Slide

14. View Slide

15. Cons
    • Expensive and complex infrastructure
    • Time consuming
    • Flaky
    

    View Slide

16. Contract tests
    

    View Slide

17. What is contract?
    

    View Slide

18. View Slide

19. View Slide

20. View Slide

21. B has changed and
    you have end-to-end tests
    

    View Slide

22. B has changed and
    you have contract tests
    

    View Slide

23. Cons
    • Expensive and complex infrastructure ✅
    • Time consuming ✅
    • Flaky ✅
    

    View Slide

24. Also catch
    • Inconsistency in API
    • Typos
    

    View Slide

25. It’s not a silver bullet tho
    

    View Slide

26. docs.pact.io
    

    View Slide

27. Pact
    • Support different languages (Ruby, JS, Go,
    PHP, Python, JVM)
    • Framework-agnostic
    • Language-agnostic contract (JSON)
    

    View Slide

28. Storage for contracts
    • Your CI
    • Your codebase (projects)
    • Pact Broker
    

    View Slide

29. Pact Broker
    • Docker image is ready
    • Webhooks to trigger checks or notifications
    • can-i-deploy tool
    

    View Slide

30. Pact Broker
    PactBroker
    PactFlow
    

    View Slide

31. View Slide

32. View Slide

33. View Slide

34. View Slide

35. View Slide

36. View Slide

37. View Slide

38. The end
    Tatiana Shepeleva
    tati.engineer
    

    View Slide