Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Avoiding common pitfalls with modern microserv...

Avoiding common pitfalls with modern microservices testing

Have you ever wondered why your microservices break in production after all the tests have passed during CI/CD? Have you ever wondered if you’re testing too much or too little? If you want to learn about common pitfalls and how to catch them at build time rather than at runtime, this session is for you!

In this session we’ll share some common battle scars from our experiences in the field. Additionally, we will introduce the testing pyramid and explain why it is important in helping to continuously deploy microservices independently without fear. We will demonstrate, through a test-driven development approach, how the combination of Pact contract testing combined with Quarkus developer joy can help prevent your microservices from breaking in production.

Holly Cummins

May 09, 2023
Tweet

More Decks by Holly Cummins

Other Decks in Programming

Transcript

  1. Holly Cummins Sr. Principal Software Engineer Red Hat @holly_cummins Eric

    Deandrea Sr. Principal Developer Advocate Red Hat @edeandrea Avoiding common pitfalls with modern microservices testing
  2. @holly_cummins @edeandrea #DevoxxUK #RedHat Imposter Disclaimer! We are not testers.

    (or even test experts) That’s ok– testing is every developer’s job!
  3. @holly_cummins @edeandrea #DevoxxUK #RedHat Netflix microservice architecture Testing with microservices

    is easy! My services are so small! Everything is decoupled! But…..
  4. @holly_cummins @edeandrea #DevoxxUK #RedHat Netflix microservice architecture Testing with microservices

    is easy! My services are so small! Everything is decoupled! But….. If you only test the points, And not the lines…. Does the thing actually work?
  5. @holly_cummins @edeandrea #DevoxxUK #RedHat “It is all that is left

    unsaid upon which tragedies are built.” - Kreia, Star Wars Knights of the Old Republic II: The Sith Lords
  6. @holly_cummins @edeandrea #DevoxxUK #RedHat “You lied to me. How many

    other lies have I been told by the Council? And how do you know that you even have the truth?” – Anakin Skywalker
  7. end-to-end tests unit tests integration tests low effort high realism

    tests with application server test REST endpoints tests with a database
  8. @holly_cummins @edeandrea #DevoxxUK #RedHat our mock our code ✔ tests

    ✘ reality our code their actual code Why mocks aren’t enough
  9. @holly_cummins @edeandrea #DevoxxUK #RedHat a mock stormtrooper “Aren’t you a

    little short for a stormtrooper?” – Princess Leia
  10. @holly_cummins @edeandrea #DevoxxUK #RedHat Demo The limitations of unit tests

    https://github.com/edeandrea/pact-quarkus-wookie-carpet-demo
  11. @holly_cummins @edeandrea #DevoxxUK #RedHat “Will someone get this big walking

    carpet out of my way?” – Princess Leia Demo The limitations of unit tests https://github.com/edeandrea/pact-quarkus-wookie-carpet-demo
  12. @holly_cummins @edeandrea #DevoxxUK #RedHat “Will someone get this big walking

    carpet out of my way?” – Princess Leia Demo The limitations of unit tests https://github.com/edeandrea/pact-quarkus-wookie-carpet-demo
  13. @holly_cummins @edeandrea #DevoxxUK #RedHat ✔ our tests ✔ their tests

    ✔ reality our code their code contract test mock functional test A better mock
  14. @holly_cummins @edeandrea #DevoxxUK #RedHat ✔ our tests ✘ their tests

    ✘ reality our code their code contract test mock functional test A better mock
  15. @holly_cummins @edeandrea #DevoxxUK #RedHat ✘ our tests ✔ their tests

    ✘ reality A better mock our code their code contract test mock functional test
  16. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests declare (Pact) Pact

    file Consumer-driven contract testing Spring Cloud Contract
  17. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests mock declare (Pact)

    Pact file Consumer-driven contract testing Spring Cloud Contract Pact
  18. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) Pact file Consumer-driven contract testing Spring Cloud Contract Pact
  19. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) contract tests verify Pact file Consumer-driven contract testing Spring Cloud Contract Pact Pact
  20. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) contract tests verify Pact file Consumer-driven contract testing ☑ rich semantic testing Spring Cloud Contract Pact Pact
  21. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) contract tests verify Pact file Consumer-driven contract testing ☑ rich semantic testing ☑ provider can ‘develop to the contract’ instead of developing speculatively (TDD) Spring Cloud Contract Pact Pact
  22. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) contract tests verify Pact file Consumer-driven contract testing ☑ rich semantic testing ☑ provider can ‘develop to the contract’ instead of developing speculatively (TDD) ⛔ existing spec assets cannot be re-purposed Spring Cloud Contract Pact Pact
  23. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) contract tests verify Pact file Consumer-driven contract testing ☑ rich semantic testing ☑ provider can ‘develop to the contract’ instead of developing speculatively (TDD) ⛔ existing spec assets cannot be re-purposed ⛔ provider needs to know who consumers are Spring Cloud Contract Pact Pact
  24. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock declare

    (Pact) contract tests verify Pact file Consumer-driven contract testing ☑ rich semantic testing ☑ provider can ‘develop to the contract’ instead of developing speculatively (TDD) ⛔ existing spec assets cannot be re-purposed ⛔ provider needs to know who consumers are ⛔ consumers can break provider CI Spring Cloud Contract Pact Pact
  25. @holly_cummins @edeandrea #DevoxxUK #RedHat contract provider OpenAPI Provider-driven contract testing

    generate (OpenAPI snapshot of current implementation) other protocol specs
  26. @holly_cummins @edeandrea #DevoxxUK #RedHat contract provider contract tests verify OpenAPI

    Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs Schemathesis Microcks
  27. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer provider contract tests verify

    OpenAPI Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs Schemathesis Microcks
  28. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock contract

    tests verify OpenAPI Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs Prism Microcks Schemathesis Microcks
  29. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock contract

    tests verify OpenAPI Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs ☑ familiar contract format Prism Microcks Schemathesis Microcks
  30. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock contract

    tests verify OpenAPI Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs ☑ familiar contract format ☑ provider does not need comms with consumers Prism Microcks Schemathesis Microcks
  31. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock contract

    tests verify OpenAPI Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs ☑ familiar contract format ☑ provider does not need comms with consumers ⛔ provider does not get insight into how API is being used (deprecation is harder) Prism Microcks Schemathesis Microcks
  32. @holly_cummins @edeandrea #DevoxxUK #RedHat contract consumer tests provider mock contract

    tests verify OpenAPI Provider-driven contract testing generate (OpenAPI snapshot of current implementation) other protocol specs ☑ familiar contract format ☑ provider does not need comms with consumers ⛔ provider does not get insight into how API is being used (deprecation is harder) ⛔ spec-based tests lack functional depth Prism Microcks Schemathesis Microcks
  33. @holly_cummins @edeandrea #DevoxxUK #RedHat Is OpenAPI enough? It has the

    same syntax, but the semantics are different. It looks the same, but the behaviour is different.
  34. @holly_cummins @edeandrea #DevoxxUK #RedHat Is OpenAPI enough? It has the

    same syntax, but the semantics are different. It looks the same, but the behaviour is different. Looks like a storm trooper. Behaves like Luke. (because it it is Luke)
  35. @holly_cummins @edeandrea #DevoxxUK #RedHat how annoying, the provider is returning

    204. the contract expects 404, so my test is broken. quarkus will return 204 by default. 204 vs 404 - it’s more about the theory behind REST...if a caller asks for a resource the server doesn't have, it should be a 404 - same way if a user types in an invalid URL into the browser ugh, it’s too late at night to care about REST theory. I’m just going to update the expectations in the test to match reality. what?! why is my other contract test broken now? 
 oh … because what I’m changing is a mock…. Based on a true story….
  36. @holly_cummins @edeandrea #DevoxxUK #RedHat “contract-first” It’s like TDD … …

    between teams for consumer-driven … with yourself, for provider-driven
  37. @holly_cummins @edeandrea #DevoxxUK #RedHat soo … microservices testing is hard

    limit end-to-end testing mocks will not be enough contract testing can rescue you
  38. @holly_cummins @edeandrea #DevoxxUK #RedHat Kubernetes Native Java with Quarkus Deployment

    Developer Joy • Quickly & easily build Kubernetes-Native Java applications • Industry leader in startup time and memory utilization for native and JVM applications • One step native executable generation • Leverage existing Java, Jakarta, MicroProfile, & Spring expertise • Imperative & reactive APIs side-by-side • Live coding with zero config https://www.infoq.com/articles/native-java-quarkus