# Testcontainers Published articles for Testcontainers. 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. ## Running AI agents in GitHub Actions with Docker Sandboxes DevFeed: [Running AI agents in GitHub Actions with Docker Sandboxes]() Original publisher: [Read original article]() Author: Jennifer Kohl Published: 2026-08-21T13:00:00Z Content type: tutorial Language: en Sources: [Docker]() Topics: [AI-assisted coding](), [ci]() Tags: [ai-agent](), [ai-coding](), [ci](), [docker](), [docker-sandboxes](), [engineering](), [github-actions](), [postgresql](), [pull-requests](), [sandboxes](), [testcontainers]() ### AI overview A tutorial on running AI coding agents in GitHub Actions inside Docker Sandboxes, emphasizing isolated execution while agents run tests, fix a seeded bug, and open a draft pull request. ### Source excerpt Run AI agents in GitHub Actions with Docker Sandboxes. See how isolated agents can run Testcontainers tests, fix code, and open draft pull requests. ## 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. ## Keycloak DevDay 2024 Videos published DevFeed: [Keycloak DevDay 2024 Videos published]() Original publisher: [Read original article]() Author: Niko Köbler Published: 2024-06-14T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [IAM](), [Multi-tenancy](), [opa](), [Apache Cassandra](), [Extension](), [Testcontainers]() Tags: [cassandra](), [community](), [conference](), [event](), [extension](), [idm](), [kerberos](), [keycloak](), [ldap](), [multi-tenancy](), [opa](), [openid-connect](), [saml](), [sso](), [testcontainers](), [videos]() ### AI overview This announcement says that recorded and live-streamed sessions from the first Keycloak DevDay conference were published online. It lists sessions covering Keycloak, including multi-tenancy, access management with OPA, extension development, Testcontainers, IAM, configuration, and Cassandra. ### Source excerpt Back in February this year, we (Sebastian and me (Niko)) hosted the very first edition of Keycloak DevDay - a one-day, community-driven conference - in Frankfurt/Main, Germany. The event was a blast and completely sold-out, plus many additional participants online in the two parallel live streams. We were able to welcome attendees from all over Europe. Thank you all for being part of this incredible event! 🙏 For all of you who couldn't attend, we have published all the recorded and live streamed sessions online on my YouTube channel: Keynote: What's Next in Keycloak (Alexander Schwartz, Red Hat) Multi-Tenancy in Keycloak (Garth Patil, Phase Two) Flexible Access Management with Keycloak & OPA (Thomas Darimont, codecentric) Best Practices for Extension Development (Sven-Torben Janus, Conciso) Extensions Development with Testcontainers (Niko Köbler, @dasniko) A Look at Keycloak from the IAM Point of View (Robert Bauer, intension) Automating Keycloak Configuration (Sophie Tauchert, Relaxdays) Ask the Maintainers Session (A. Schwartz, T. Darimont, S. Schuster) IAM Doomsday Prepper (Maik Kingma) Keycloak Cassandra Datastore (Dominik Schlosser) The complete playlist can be found here. We are currently preparing the next edition "Keycloak DeveloperDay 2025". If you want to contribute, please get in touch with us (Sebastian & Niko)! Expect more information in the next weeks and months. Looking forward to have you and your colleagues & team members as attendees! ## 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 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 -> ## Using H2 as a Test Database Product with jOOQ DevFeed: [Using H2 as a Test Database Product with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-19T07:25:43Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [in-memory database](), [Testing](), [Java](), [SQL](), [sql-server]() Tags: [compatibility-mode](), [database](), [h2](), [in-memory-database](), [integration-testing](), [java](), [jooq](), [jooq-in-use](), [sql](), [sql-server](), [testcontainers](), [testing](), [vendor-agnosticity]() ### AI overview This article explains the trade-offs of using H2 as a test database for Java applications with jOOQ. It shows why SQL that works on H2 may require syntax changes on SQL Server, describes H2 compatibility modes, and notes that jOOQ generates SQL for H2's native dialect rather than its compatibility modes. ### Source excerpt The H2 database is an immensely popular in-memory database product mostly used by Java developers for testing. If you check out the DB-Engines ranking, it ranks 50th, which is quite impressive, as this rank outperforms products like: CockroachDB Ignite Single Store (previously MemSQL) Interbase (which was forked as Firebird) Ingres (which is a predecessor to ... Continue reading Using H2 as a Test Database Product 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