Repository files navigation

You know the feeling...

It's Friday afternoon. You're late with your feature and about to push your latest Spring Boot application to production.

Your stomach tightens.

"Did I test everything properly? What if something breaks? What if I become the reason for that 2 AM emergency call on the weekend?"

• Buggydeployments that damage your team's reputation
• Latenightsdebugging issues that should've been caught earlier
• Cripplinganxiety every time you push to production
• Technicaldebt that grows more painful with each sprint
• Lostweekendsfixing what should never have broken

Imagine:

• Pushing to production on Friday afternoonwithout a second thought
• Your manager praising your code'srock-solidreliability
• Being the go-to person forsolving complex testing challenges
• Acceleratingyourcareer as you deliver higher quality code faster
• Feelingabsolute peace of mind knowing your tests have you covered

Are you tired of:

• Spending countless hours debugging production issues that should have been caught in testing?
• Feeling anxious about deploying on Fridays because your test coverage isn't comprehensive?
• Wrestling with complex microservice architectures that are difficult to test properly?
• Copying and pasting test code from Stack Overflow without understanding the underlying principles?
• Missing deadlines because of unexpected bugs and regressions?
• Mindlessly applying cargo cult testing practices that don't fit your application's needs?

TheTesting Spring Boot Applications Masterclass transforms you from feeling uncertain about your application's reliability to being confident in your testing strategy, making you a moreproductive,efficient, andvaluabledeveloper.

Automated testing is (unfortunately)often neglected, but it’s the key to building robust, reliable Spring Boot applications and shipping features with confidence.

This Masterclass will teach you everything you need to know about testing Spring Boot applications—from unit tests to end-to-end tests—so you can stop guessing and start delivering with peace of mind.

What You’ll Gain:

• Confidence in Every Deployment: Push to production—even on Fridays—without breaking a sweat.
• Master Testing Best Practices: Learn to test every layer: databases, messaging, HTTP communication, and more.
• Efficiency and Joy in Testing: Testing doesn’t have to be a frustrating chore. Let’s make it fun, fast, and effective!

"After taking Philip's course, I deployed on a Friday afternoon for the first time in my career. My confidence in our test suite is that strong now."

— Senior Developer at a Fortune 500 Company

"Philip has made a fantastic overview of the full testing landscape of Spring. The videos are clear and explain details and common pitfalls in great depth."

— Wim Deblauwe, Experienced Java Developer

"This course was a complete game-changer for me. I went from dreading tests to actually enjoying writing them. And more importantly, my boss noticed."

— Java Developer with 5 years experience

"I would highly recommend Masterclass for anybody working with Spring Boot applications."

— Siva, Java Developer and Tech Blogger

• Production-Grade Application: You'll work with a real microservice architecture that mirrors actual business applications, not oversimplified examples.
• Comprehensive Coverage: From basic unit tests to complex integration scenarios, you'll learn testing strategies for every layer of your application.
• Practical Approach: Every concept is taught through hands-on examples that you can immediately apply to your projects.

Throughout the course you'll learn how to effectively use well-known testing libraries like JUnit 5, Mockito, Awaitility, LocalStack, Testcontainers, Selenide, WireMock, MockWebServer, and JsonPath.

To mirror a typical modern microservice architecture, the demo application uses the following tech stack and infrastructure components:

• Keycloak (open source identity and access management solution) to secure parts of the frontend and backend with OpenID Connect/OAuth 2.0
• Amazon SQS (Simple Queuing Service) to demonstrate testing asynchronous message processing
• PostgreSQL (RDBMS) to demonstrate testing with a relational database
• Single Page Application Frontend with React and TypeScript
• Spring Boot backend with Java
• Dependency on a remote REST API to demonstrate testing HTTP communication

Even though the technical setup for your day-to-day projects might differ, the testing recipes you'll learn are generic, and you can easily apply them for your tech stacks.

»Enroll now for the Testing Spring Boot Applications Masterclass.

💡Money-back guarantee: Not satisfied? Get a full refund within 60 days, no questions asked.

main branch:

code-along branch:

• Course Landing Page with FAQ
• Course Overview
• Course Login
• Password Reset

Mandatory requirements:

• Java 21 (JDK flavour (OpenJDK/Azul/Oracle) does not matter). For the correct Java version setup I can recommendJEnv (Mac/Linux) and theMaven Toolchains Plugin (Windows)

$ java -versionopenjdk version "21.0.1" 2023-10-17 LTSOpenJDK Runtime Environment Temurin-21.0.1+12 (build 21.0.1+12-LTS)OpenJDK 64-Bit Server VM Temurin-21.0.1+12 (build 21.0.1+12-LTS, mixed mode)

• Docker Engine (Community Edition is enough) and Docker Compose:

$ docker versionClient: Docker Engine - Community Version:           20.10.6 API version:       1.41 Go version:        go1.13.15 Git commit:        370c289 Built:             Fri Apr  9 22:47:17 2021 OS/Arch:           linux/amd64 Context:           default Experimental:      trueServer: Docker Engine - Community Engine:  Version:          20.10.6  API version:      1.41 (minimum version 1.12)  Go version:       go1.13.15  Git commit:       8728dd2  Built:            Fri Apr  9 22:45:28 2021  OS/Arch:          linux/amd64  Experimental:     false$ docker-compose versiondocker-compose version 1.26.2, build eefe0d31docker-py version: 4.2.2CPython version: 3.7.7OpenSSL version: OpenSSL 1.1.1g  21 Apr 2020

Optional requirements:

• Maven >= 3.6 (the project also includes the Maven Wrapper).

When using Maven from the command line, make sure./mvnw -version reports the correct Java version:

$ ./mvnw -versionApache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)Maven home: /home/rieckpil/.m2/wrapper/dists/apache-maven-3.8.4-bin/52ccbt68d252mdldqsfsn03jlf/apache-maven-3.8.4Java version: 17.0.1, vendor: Eclipse Adoptium, runtime: /usr/lib/jvm/jdk-17.0.1+12Default locale: en_US, platform encoding: UTF-8OS name: "linux", version: "5.4.0-92-generic", arch: "amd64", family: "unix"

• IntelliJ IDEA or any IDE/Code Editor (Eclipse, NetBeans, Code, Atom, etc.)

Assuming your local setups meets all requirements as stated above, you can now start the application:

1. Make sure your Docker Engine is up- and running
2. Start the required infrastructure components withdocker-compose up
3. Run the application with./mvnw spring-boot:run or inside your IDE
4. Accesshttp://localhost:8080 for the application frontend
5. (Optional) Accesshttp://localhost:8888 for the Keycloak Admin interface

Valid application users:

• duke (passworddukeduke)
• mike (passwordmikemike)

Replace./mvnw withmvnw.cmd if you're running on Windows.

Run allunit tests (Maven Surefire Plugin):./mvnw test

Run allintegration & web tests (Maven Failsafe plugin):

1. Make sure no conflicting Docker containers are currently running:docker ps
2. Make sure the test classes have been compiled and the frontend has been built and is part of thetarget/classes/public folder:./mvnw package -DskipTest
3. Execute./mvnw failsafe:integration-test failsafe:verify

Runall tests together:

1. Make sure no conflicting Docker container is currently running:docker ps
2. Execute./mvnw verify

Skip all tests (don't do this at home):

1. Execute./mvnw -DskipTests=true verify

See thisGitHub issue for resolving it.

For skipping the frontend build, add-Dskip.installnodenpm -Dskip.npm to your Maven command, e.g.,./mvnw test -Dskip.installnodenpm -Dskip.npm.

You can pass-DskipTests to./mvnw package if you experience test failures:./mvnw package -DskipTests to build the application without running any unit test.

Next, make sure you have the latest version of this project (rungit pull) and ensure thebuild status is green.

If you still encounter any test failures, pleasecreate an issue and include information about your environment.

Adjust thedocker-compose.yml file and remove the setup to import Keycloak configuration on the startup:

version:'3.8'services:# ...keycloak:image:quay.io/keycloak/keycloak:18.0.0-legacyenvironment:      -KEYCLOAK_USER=keycloak      -KEYCLOAK_PASSWORD=keycloak      -DB_VENDOR=h2ports:    -"8888:8080"

Next, start everything withdocker-compose up and watch the following video toconfigure Keycloak manually.