Andre Hofmeister

@hovfefe
91 Followers
19 Following
188 Posts
Maintaining #testcontainers | Contributing to OSS | Automating builds, tests and infrastructures | Making devs happy | At ZEISS Group | Docker Captain
📍Behind a keyboard or guitar
Websitehttps://www.andrehofmeister.com
GitHubhttps://github.com/HofmeisterAn
The new #testcontainers for #dotnet release has arrived: https://github.com/testcontainers/testcontainers-dotnet/releases/tag/4.11.0. Version 4.11 comes with new modules, bug fixes, and improvements, plus OpenSSF Scorecard analyses for extra trustworthiness. I've also got an update ready for the Docker.DotNet client, which in the next release will bring performance improvements, better resource usage, lots of fixes, and support for .NET's native HTTP handler 💪.
Release 4.11.0 · testcontainers/testcontainers-dotnet

What's Changed Thanks to all contributors. Once again, really great contributions from everyone 🤝. The NuGet packages for this release have been attested for supply chain security using actions/att...

GitHub
With the new design and structure, adding or extending handlers is much easier. SSH support is coming soon.

I've started refactoring Docker.DotNet and introducing a more modern, reliable implementation.

Just added a clean builder API for creating Docker client instances. With help from the community, it now supports the .NET native HTTP handlern. No more mandatory legacy, slow implementation (opt-in for now): https://github.com/testcontainers/Docker.DotNet?tab=readme-ov-file#usage. #docker #dotnet

@tim_abell I often think vice versa would be cool, using a commit hash to generate a NuGet package on the fly or on demand instead of publishing every time. It would be especially helpful for multi-repo projects and for fast testing with many internal dependencies.
@mikaellundin Dev Containers is great. I use it often together with Testcontainers. You find more information here: https://dotnet.testcontainers.org/. Our examples, modules, including the tests, are a good place to get started: https://github.com/testcontainers/testcontainers-dotnet. LMK if you need any help.
Testcontainers for .NET

I've put together a few slides for future #testcontainers for #dotnet talks. If you're interested in discussing #testcontainers, let me know. Feedback on the slides is welcome as well: https://andrehofmeister.com/en/testcontainers-for-dotnet.
Testcontainers for .NET

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.

Docker.DotNet is now compatible with the latest #docker Engine v29 (https://github.com/testcontainers/Docker.DotNet/releases/tag/v3.131.0). Please note that backward compatibility with earlier API versions is limited due to the project's current structure. I will address this limitation in upcoming releases. #dotnet
Thanks again to everyone who contributed :tc-love:

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/.

Release 4.9.0 · testcontainers/testcontainers-dotnet

What's Changed This release adds a new configuration (DOCKER_API_VERSION) that lets you pin and downgrade the Docker Engine API version. This was needed because Docker Engine v29 introduced breakin...

GitHub