I never expected such an amazing journey when I started working on #testcontainers for #dotnet years ago. I've met many great people and learned a lot. I'm truly grateful for all of it. I never imagined the packages would one day pass 150M+ downloads!
Check out Testcontainers (https://testcontainers.com/) and test against real dependencies with confidence.
Realistic test environments often turn into complex beasts. The TCI framework adds structure and control on top of #Testcontainers—without sacrificing flexibility.
Alexander Bierler explains how.
Read #JAVAPRO now:https://javapro.io/2025/10/10/supercruising-with-testcontainers-making-tests-faster-and-more-flexible/
#CI #DevOps #Java #Frameworks #OpenSource
A new #testcontainers for #dotnet release is available. This release supports .NET 10 and ensures compatibility with Docker Engine v29: https://github.com/testcontainers/testcontainers-dotnet/releases/tag/4.9.0. I'm working on updating Docker.DotNet for full v29 support, so expect a new version soon /cc @docker.
Check out the new available modules like Playwright, Grafana, or my favorite this release, Toxiproxy. It's a really interesting tool for pushing testing further: https://dotnet.testcontainers.org/modules/toxiproxy/.
Good day folks. How many of you are still battling to repair issues related to testcontainers, java-docker and the Docker 29 release?
If you're updating to #docker engine v29 and using Docker.DotNet, make sure to pin the API version to 1.44 (or similar). v29 breaks the library. More details here: https://github.com/moby/moby/releases/tag/docker-v29.0.0.
I'm working on making Docker.DotNet compatible with v29. An updated version of #testcontainers for #dotnet will be available soon.
A few self-hosters have laughed about the Azure and AWS outages. I think a few of them are now dealing with some outages for tools because #Docker 29.0.0 increased the minimum API version from 1.24 to 1.44, which caused some tools like #Traefik to fail. Their GitHub issue page got quickly flooded with issues. The good thing, people also shared workarounds to get them quickly back on track. I felt sorry for the stress they got in the last days. The Traefik maintainers managed to fix it pretty quickly and shipped 3.6.1, and all is good again.
The question would be, why haven't they seen that one coming? Wasn't it clearly communicated from #Docker, or haven't paid #Traefik maintainers paid enough attention?
The fall-out of that change is quite interesting. It will affect a lot of dependencies like #testcontainers, which have shipped 2.0.2, being compatible with Docker 29.0.0. Seems like some maintainers have some work to do, wish them well.
An important note in the #docker 29.0 release notes is the deprecation of older API versions. Previously Docker was supporting clients going all the way back to v1.12.0 released in 2016. The engine now defaults to requiring v25.0 clients released on 2024-01-19.
Tools that mount the docker socket may need upgrades or workarounds. Breakages have been seen with #watchtower, #portainer, #traefik, and #testcontainers.
https://dotnet.testcontainers.org/test_frameworks/xunit_net/ - #TestContainers for #dotNET allows spinning up #Docker #containers in the middle of #xUnit #tests.
https://node.testcontainers.org/quickstart/usage/ - #TestContainers for #Node allows quickly spinning up #containers in the middle of anything like #Tests. I didn't realize there was more to the docs than the blank first page.
Aaaand #Testcontainers joins the club of libraries removing methods in major versions without a deprecation period in advanced. Thanks for nothing.
Ускоряем сборку с помощью Gradle Build Services
На одном из проектов, над которым я работаю, я столкнулся с постоянно растущим временем сборки проекта на CI. Оказалось, что причина была в интеграционных тестах работы с БД в модулях с использованием Testcontainers. Каждый модуль запускал свой контейнер и в придачу применял на них миграции Liquibase. В данной статье я хочу рассмотреть способ решения этой проблемы с помощью Gradle Build Services — механизма для разделения состояния между задачами. Цель - использовать только один контейнер PostgreSQL на всю сборку, и настроить все тестовые задачи на его использование.
We shipped a new version of #testcontainers for #dotnet yesterday! Really proud of the last two releases. They include some great new features along with lots of performance and stability improvements. Big thanks to all the contributors: https://github.com/testcontainers/testcontainers-dotnet/releases/tag/4.8.0.
Your tests block your flow? TCI extends #Testcontainers with pre-warmed infrastructure, parallel execution & leak detection. Alexander Bierler shares how to stop waiting and start shipping.
Read #JAVAPRO now:https://javapro.io/2025/10/10/supercruising-with-testcontainers-making-tests-faster-and-more-flexible/
Enhance the Spring Boot developer experience with Arconia Dev Services: zero-code and zero-config infrastructure provisioning. Add one dependency. That's it!
Databases, event queues, observability platforms, AI services and more. All powered by Testcontainers!
#Java #SpringBoot #Arconia #Testcontainers #DeveloperExperience
https://www.thomasvitale.com/arconia-dev-services-spring-boot/
Waiting for tests wastes time—or money. Alexander Bierler shows how a framework on top of #Testcontainers improves parallelization and caching to reduce test runtimes by 50%.
Want faster CI?
👉 Read #JAVAPRO: https://javapro.io/2025/10/10/supercruising-with-testcontainers-making-tests-faster-and-more-flexible/
General #Testcontainers question.
We have Docker running in WSL. We don't have "Docker for Windows". Is there any way to get TestContainers to play ball with a WSL?
Edit: Managed to get it working.
What if we could easily spin up containers for services that our tests depend on?
Read more here:
https://www.devleader.ca/2024/03/27/c-testcontainers-for-mongodb-how-to-easily-run-local-databases/
I really enjoy maintaining #testcontainers for #dotnet, but keeping up with modules beyond my focus on Docker.DotNet is getting a bit tough. I'd love to see more people from the community help maintain modules and keep the project strong. Join the discussion 🙏: https://github.com/testcontainers/testcontainers-dotnet/discussions/801#discussioncomment-14477998.
How to run #PostgreSQL in #Testcontainers with SSL/TLS + client certificates 🔐🐘with #Java
Covers cert generation, config (postgresql.conf / pg_hba.conf), JDBC, & psql.
https://ozkanpakdil.github.io/posts/my_collections/2025/09-12-testcontainers-postgresql-ssl/
Starting to learn how to use #testcontainers with #python for #pyinfra. It's an itch I had.
Been meaning to build up everything with pyinfra. But I need tests. In #ansible world, I had tests for everything using Molecule. It worked well enough, but was quite complex.
However, with pyinfra, the tests can be isolated integration test containers! 😎
Now I can go crazy with the amount of tests for every operation done. 😆
