1-13-25 - Quarkus Testing Landscape

I will review the various types of tests in Quarkus. I’ll cover unit, integration, mocking, spying, contract testing, and Playwright. I'll also share patterns for testing inner and outer loop processes.

Recording: https://www.youtube.com/live/hxYZHIA1xWc

Transcript

1. @edeandrea Quarkus Testing Landscape Eric Deandrea, Red Hat Java Champion | Senior Principal Developer Advocate edeandrea@redhat.com
2. @edeandrea 2 • Java Champion • 25+ years software development experience • ~11 years DevOps Architect • Contributor to Open Source projects Quarkus Spring Boot, Spring Framework, Spring Security LangChain4j (& Quarkus LangChain4j) Wiremock Microcks • Boston Java Users ACM Chapter Board Member • Published Author About Me
3. @edeandrea • Showcase & explain Quarkus, how it enables modern Java development & the Kubernetes-native experience • Introduce familiar Spring concepts, constructs, & conventions and how they map to Quarkus • Equivalent code examples between Quarkus and Spring as well as emphasis on testing patterns & practices 3 https://red.ht/quarkus-spring-devs
4. @edeandrea 4 https://jchampionsconf.com/speakers.html#deandreaCard https://www.jfokus.se/talks/2070 https://devnexus.com/presentations/test-driven-development-it-s-easier-than-you-think https://www.meetup.com/central-iowa-java-users-group/events/305348139 https://www.meetup.com/ottawa-java-user-group/events/305468016 https://www.meetup.com/montreal-jug/events/304716668
5. @edeandrea @edeandrea Why the obsession?
6. @edeandrea 6 https://quotefancy.com/quote/966305/Henry-Rollins-The-more-you-own-the-more-it-owns-you
7. @edeandrea 7
8. @edeandrea 8
9. @edeandrea 9
10. @edeandrea 10 https://hollycummins.com/modern-microservices-testing-pitfalls-devbcn
11. @edeandrea 11
12. @edeandrea 12
13. @edeandrea @edeandrea How?
14. @edeandrea The “normal” stuff • Unit testing ◦ Isolate a “unit” within the application as a standalone entity ◦ Use mocking / spying to control dependencies of the unit during test ◦ Test all potential outcomes of a particular unit • Integration testing ◦ Treat application as a black box ◦ Downstream services (db, message brokers, etc) need to be available ◦ Application should be run & tested as its intended to be deployed 14
15. @edeandrea The “normal” stuff • Mocking ◦ Complete mock / “fake” ◦ User must define interaction(s) ◦ Default behavior if not defined: do nothing ◦ Can verify intended behaviors occurred after test (verification-based testing) • Spying ◦ Partial mock / “real” ◦ User doesn’t need to define interaction(s) ◦ Default behavior if not overridden: perform actual operation ◦ Useful for “watching” things during tests & verifying intended behaviors occurred (verification-based testing) 15 These don’t have to be object-based!!!
16. @edeandrea Quarkus Superheroes 16 https://github.com/quarkusio/quarkus-super-heroes
17. @edeandrea 17 https://hollycummins.com/modern-microservices-testing-pitfalls-devbcn
18. @edeandrea @edeandrea UI Testing
19. @edeandrea 19 Quarkus Quinoa https://docs.quarkiverse.io/quarkus-quinoa/dev/index.html Quinoa Build Runtime
20. @edeandrea 20 Quarkus Quinoa Testing https://docs.quarkiverse.io/quarkus-quinoa/dev/testing.html
21. @edeandrea @edeandrea UI Testing Without the UI
22. @edeandrea 22 Quarkus Playwright https://docs.quarkiverse.io/quarkus-playwright/dev/index.html Cross-browser e2e tests for web apps
23. @edeandrea 23 Quarkus Quinoa Playwright https://docs.quarkiverse.io/quarkus-quinoa/dev/testing.html Combine Quinoa & Playwright
24. @edeandrea @edeandrea Any time left?
25. @edeandrea @edeandrea Thank you!
26. @edeandrea 26 https://quarkus.io @quarkusio https://quarkusio.zulipchat.com