nammayatri VS Testcontainers

If your project uses Nix, checkout services-flake for running services via Nix.

https://github.com/juspay/services-flake

We actually do this in Nammayatri, an OSS project providing "Uber" for autos in India.

https://github.com/nammayatri/nammayatri

There is a services-flake module allowing you to spin the entire nammayatri stack (including postgres, redis, etc.) using a flake app. Similarly, there's one for running load test, which is also run in Jenkins CI.

NY is in the early stages of growth, and there are definitely areas for improvement. Key priorities are improving affordability, customer experience & support and driver availability. But what has differentiated NY so far is its 100% openness in every decision. It's built on Beckn protocol (like open Email/SMTP or TCP/IP protocols, anyone can implement it). NY is part of ONDC network, so anyone can do what NY has done so far. Initial response is encouraging, with 5L+ customers, ~50k drivers, ~4.8 app rating (Open data here). Open Roadmap here. Complete source code here. Anyone can contribute to the open problems through city hackathon. DM your thoughts and happy to hope into a call.

except the parent is wrong (at least the Java impl). see:

https://github.com/testcontainers/testcontainers-java/blob/m...

https://github.com/testcontainers/testcontainers-java/blob/m...

> I wonder if Rancher Desktop, et al, works with testcontainers.org?

I don't use testcontainers myself, but it looks like as long as you are using Rancher Desktop >= 1.0.1 you should be just fine.[1]

[1] https://github.com/testcontainers/testcontainers-java/issues...

Thanks for the feedback. You are right, and there are some other mock-up alternatives as well, a good one for developers https://testcontainers.com/

In this article, we will explore how to use Testcontainers and Exposed, a lightweight ORM framework for Kotlin, to create a controlled environment for testing MySQL Database operations.

Unfortunately, it still remains hard to use Testcontainers because of how wedded it is to junit4, five years after the release of junit 5. https://github.com/testcontainers/testcontainers-java/issues/970

Finally, we put the directory with generated contents (HTML, CSS, JS) into a tarball. Testcontainers library allows to copy files from a container to the OS but not directories. That’s why we need an archive inside the SchemaSpy container.

This repository provides a BuildImageTest that uses the buildpack to create a native image. It then tests the native image, using Testcontainers and JUnit. Building the native image with AOT processing, as part of a test, takes minutes not seconds, and should not be part of normal "inner loop" development. So the BuildImageTest is in a separate sourceSet and can be executed independently. This is a very powerful pattern, that I'm just getting started with. I would love to hear your thoughts on this pattern or other alternatives to it.

The list goes on. Check out the full list of Testcontainer modules.

Test-Container Java

TestContainers looks Java specific... or are you talking about something else?