When writing integration tests with Testcontainers, a significant portion of the code gets dedicated to declaring, configuring, and starting the required container
Similar to a REST API, an Amazon SQS listener is an entry point to our application. While we can easily test our
Testcontainers offers several initialization strategies for our Docker containers when writing integration tests. Depending on the Docker image we use for our
MongoDB is one of the NoSQL databases that Spring Boot offers great testing support for. Like all other test slice annotations from
Good old web tests – extremely valuable, sometimes hard to maintain, and annoying once they get flaky. If you are familiar with
Recently I introduced Testcontainers for a Kotlin based Spring Boot application. I jumped right into the setup and immediately ran into an
If your Spring Boot application integrates AWS services like S3, SNS, or SQS, you might wonder how to write effective integration tests.
Ensuring your application is working properly is a critical part of continuous integration and delivery. Unit tests help you to test your
Integration tests for your Jakarta EE application are essential. Testing the application in a full setup will ensure all of your components
Testcontainers is a game-changing library for writing integration and end-to-end tests. With the advent of Docker, we can conveniently start infrastructure components
