I built testcontainers for Gleam and the name was already taken. Twice. Let me start with the name, because it tells you everything. The canonical testcontainers library for the JVM ecosystem is called testcontainers . There is also one for Elixir, and it is called testcontainers . Then someone built a Gleam wrapper around the Elixir one and published it as testcontainers_gleam . By the time I showed up wanting to build something native for Gleam, both testcontainers and testcontainers_gleam were gone. So the library is called testcontainer . Singular. Not because I think one container is enough. Because I arrived third. So, why build it at all testcontainers_gleam is not a bad library. I want to be clear about that. It does what it says. It wraps the Elixir Testcontainers implementation and exposes it to Gleam code. If you are already in a mixed Elixir/Gleam project where that Elixir dep is sitting in your tree anyway, it is a completely reasonable choice and it probably saves you an afternoon.…