# Testcontainers Testcontainers is an open-source library that provides throwaway, lightweight Docker-container instances of test dependencies such as databases, message brokers, and web browsers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## API Mocking and Testing With Microcks DevFeed: [API Mocking and Testing With Microcks]() Original publisher: [Read original article]() Author: Andrei Branza Published: 2026-08-22T23:20:24Z Content type: tutorial Language: en Sources: [Baeldung]() Topics: [Mocking](), [Testcontainers](), [API](), [OpenAPI Specification](), [Microservices](), [Docker Compose](), [Docker](), [Kafka](), [Amazon Simple Queue Service (SQS)](), [GraphQL](), [gRPC](), [Jenkins]() Tags: [api](), [compose](), [docker](), [how-to](), [kafka](), [kubernetes](), [mocking](), [openapi](), [popular](), [testcontainers](), [testing](), [testing-popular-testcontainers]() ### AI overview This tutorial explains how to use Microcks with Testcontainers to generate API mocks from contracts and run conformance tests against real implementations. It covers importing an OpenAPI contract, starting Microcks in a JUnit 5 test, calling generated mock endpoints, and integrating mocking and testing into delivery workflows. ### Source excerpt Learn how to use Testcontainers integration to spin up Microcks inside a JUnit5 test. The post API Mocking and Testing With Microcks first appeared on Baeldung. ## Scaling out Distroless adoption With AI DevFeed: [Scaling out Distroless adoption With AI]() Original publisher: [Read original article]() Author: Jia Yee Chong Published: 2026-06-22T00:00:00Z Content type: article Language: en Sources: [Grab Tech]() Topics: [Security](), [migration](), [Dockerfile](), [Vulnerabilities](), [make](), [ci](), [configuration](), [Docker](), [Docker Image](), [Testcontainers](), [MySQL]() Tags: [artificial-intelligence](), [ci](), [containers](), [devsecops](), [docker](), [docker-image](), [engineering](), [migration](), [mysql](), [security](), [testcontainers](), [testing](), [vulnerabilities]() ### AI overview Grab describes migrating services from heavy base images to Distroless images to reduce security risks and eliminate unnecessary binaries and associated CVEs. The article explains the runtime-failure risks of this migration and presents medium tests using Docker images, Testcontainers, and network proxies to verify configuration and runtime dependencies in CI. ### Source excerpt Distroless adoption at Grab Grab is migrating from heavy base images to Distroless images to reduce security risks. By limiting each container to the application and its runtime dependencies, we shed non-essential binaries and associated Common Vulnerabilities and Exposures (CVEs). This migration is more than a compliance mandate; it is a strategic security decision to build a more resilient environment. Why Distroless requires rigorous testing Distroless adoption risk: Runtime failure Shifting to Distroless images introduces a critical technical risk: Runtime Failure. A service might build perfectly in Continuous Integration (CI), but fail at the deployment stage due to: Missing shared objects: Binaries might require specific libraries (.so files) present in Ubuntu but absent in Distroless. Implicit links: Third-party tools might expect specific system utilities or directory structures. Testing is required to ensure two things: The service spins up with the correct configuration. All runtime dependencies remain intact. Scaling this verification across thousands of services manually? That would take years, unless we found a way to automate the trust. The testing methodology As we perform changes to the Dockerfile definition of our services, it is important for us to include the corresponding test strategy to ensure that the changes that we make do not introduce a regression to our running services. Assessing the change introduced to our services, the lowest possible testing boundary would be that of what we define as medium tests in Grab. Medium tests in Grab At Grab, we categorize our test suites into 3 main sizes: small, medium and large. Small tests refer to functional tests whereby mocks are introduced via dependency injection. Large tests refer to end-to-end tests that run on actual services in our staging environment where nothing is mocked. Figure 1: Architecture diagram of a medium test environment Medium tests sit between the small and large tests. External ## Catch Bugs Early with Testcontainers: Shift-Left Testing Made Easy DevFeed: [Catch Bugs Early with Testcontainers: Shift-Left Testing Made Easy]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-05-15T00:00:00Z Content type: article Language: en Sources: [Abhimanyu Saharan]() Topics: [Testcontainers](), [Code]() Tags: [bugs](), [code](), [docker](), [integration](), [shift-left](), [speed](), [testcontainers](), [testing]() ### AI overview The article explains how Testcontainers can run integration tests with real services to catch bugs earlier and improve software reliability, speed, and confidence. ### Source excerpt Catch bugs early by running integration tests with real services using Testcontainers, improving reliability, speed, and confidence in your code. ## When to Use jOOQ and When to Use Native SQL DevFeed: [When to Use jOOQ and When to Use Native SQL]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-12-08T13:53:02Z Content type: comparison Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [rdbms](), [Test-driven development](), [Testcontainers]() Tags: [cons](), [examples](), [jdbc](), [jdbctemplate](), [jdbi](), [jooq](), [jooq-in-use](), [native-sql](), [plain-jdbc](), [plain-sql-templating](), [rdbms](), [sql](), [sql-json](), [stored-procedures](), [tdd](), [testcontainers]() ### AI overview This comparison explains when to use the jOOQ API and when to use native SQL for complex queries. It describes jOOQ's advantages for dynamic SQL, multiple database dialects, type safety, data mapping, stored procedures, security, exports, and diagnostics, while noting usability drawbacks for large static queries with many CTEs or derived tables. ### Source excerpt A frequently encountered doubt people have when using jOOQ is to decide when a "complex" query should be written using jOOQ API vs. when it should be implemented using native SQL. The jOOQ manual is full of side by side examples of the same query, e.g. Using jOOQ: Using native SQL: In the native SQL ... Continue reading When to Use jOOQ and When to Use Native SQL -> ## How to setup remote docker host DevFeed: [How to setup remote docker host]() Original publisher: [Read original article]() Published: 2022-09-26T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Docker](), [Image](), [docker images](), [Testcontainers](), [Amazon EC2](), [Amazon Web Services](), [Linux](), [TLS (Transport Layer Security)](), [x86]() Tags: [arm](), [aws](), [containers](), [docker](), [docker-images](), [ec2](), [how-to](), [integration-test](), [linux](), [remote](), [tls](), [x86]() ### AI overview This tutorial explains how to set up a remote Docker host for integration tests when required ARM images are unavailable. It uses a Linux x86_64 AWS EC2 machine, configures TLS access to the Docker daemon, and connects a local Docker client to the remote host. ### Source excerpt Not all docker images are available for ARM architecture (hopefully this will improve over time). Right now I'm working on a project where images for ARM are not available. Emulation works ok (but slow) most of the time. Lately, I stumbled upon an interesting performance/startup issue when running amd64-based containers using testcontainers in an integration test. Read more ## How to Integration Test Stored Procedures with jOOQ DevFeed: [How to Integration Test Stored Procedures with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-22T12:36:00Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Testing](), [Database](), [Testcontainers](), [Java](), [PostgreSQL]() Tags: [code](), [code-generation](), [database](), [gradle](), [how-to](), [integration-test](), [integration-testing](), [java](), [jooq](), [jooq-in-use](), [junit](), [maven](), [stored-procedures](), [testcontainers](), [unit-test]() ### AI overview This tutorial explains how to integration-test database stored procedures and functions with Java, jOOQ, Testcontainers, and JUnit. It shows how to run PostgreSQL in Testcontainers, generate jOOQ classes for stored procedures, and reuse Java test infrastructure instead of manually binding to procedures through JDBC. ### Source excerpt When you write stored procedures and functions in your database, you want to ensure their correctness, just like with your Java code. In Java, this is done with unit tests, typically with JUnit. For example, if you have the following code in Java: Then, you might write a test like this: But how do we ... Continue reading How to Integration Test Stored Procedures with jOOQ -> ## Fast and Stable MongoDB-Based Tests in Spring DevFeed: [Fast and Stable MongoDB-Based Tests in Spring]() Original publisher: [Read original article]() Author: piotr-kubowicz Published: 2020-12-07T00:00:00Z Content type: tutorial Language: en Sources: [Backend Development on nexocode]() Topics: [MongoDB](), [Testcontainers](), [Spring Boot](), [Database](), [Software Engineering]() Tags: [database](), [embedded](), [how-to](), [kotlin](), [linux](), [mongodb](), [performance](), [software-engineering](), [spring](), [testcontainers](), [testing](), [tests](), [tutorials]() ### AI overview A tutorial for replacing Flapdoodle Embedded Mongo with Testcontainers in Spring applications. It explains problems caused by multiple embedded MongoDB instances, shows how to set up MongoDB with Testcontainers, and discusses performance measurement using Linux tools. ### Source excerpt If your Spring application uses MongoDB, there is one question you will have to answer at some point: how to set up a database instance for your tests. Until early 2020 there was not much choice and the default was to use 'embedded Mongo' - my team was no exception. At some point, however, we realised that embedded Mongo was turning our builds into a nightmare. This ultimately prompted us to migrate our code to a tool getting much hype recently - Testcontainers. ## Quarkus and Testcontainers DevFeed: [Quarkus and Testcontainers]() Original publisher: [Read original article]() Published: 2020-11-28T16:45:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [Quarkus](), [Testcontainers](), [Testing](), [Databases](), [Docker](), [Object-relational mapping](), [SQL]() Tags: [databases](), [docker](), [kafka](), [orm](), [postgres](), [quarkus](), [schema](), [sql](), [testcontainers](), [testing](), [tests]() ### AI overview A tutorial on integrating Quarkus test resources with Testcontainers for JUnit tests. It explains the limitations of combining the Quarkus and Testcontainers JUnit extensions, recommends dynamically assigned Docker ports, and presents Quarkus test resources as an alternative for managing container lifecycles and database setup. ### Source excerpt Table of Contents Bonus: Schema Creation The Testcontainers project is invaluable for spinning up containerized resources during your (JUnit) tests, e.g. databases or Kafka clusters. For users of JUnit 5, the project provides the @Testcontainers extension, which controls the lifecycle of containers used by a test. When testing a Quarkus application though, this is at odds with Quarkus' own @QuarkusTest extension; it's a recommended best practice to avoid fixed ports for any containers started by Testcontainers. Instead, you should rely on Docker to automatically allocate random free ports. This avoids conflicts between concurrently running tests, e.g. amongst multiple Postgres containers, started up by several parallel job runs in a CI environment, all trying to allocate Postgres' default port 5432. Obtaining the randomly assigned port and passing it into the Quarkus bootstrap process isn't possible though when combining the two JUnit extensions. ## Testcontainers DevFeed: [Testcontainers]() Original publisher: [Read original article]() Published: 2019-07-18T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Testcontainers](), [Testing](), [Docker](), [Redis]() Tags: [docker](), [integration](), [redis](), [services](), [testcontainers](), [testing]() ### AI overview A tutorial on using Testcontainers to run Docker containers for integration tests. It demonstrates testing communication with a live Redis instance without manually preparing infrastructure. ### Source excerpt Recently I've found a very interesting project which allows to spin up docker containers for test purposes. Writing tests checking integration with external services is not an easy task. With testcontainers library it gets simpler because you can have external service up and running just for your test in a couple of lines of code. Read more