Testcontainers VS Pact JVM

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?

API Contract Testing might be worth exploring. Gives you the ability to run it quickly locally or in CI/CD. A centralized way to validate if your changes broke another service might also be interesting. That series of videos from the same team is gold: https://docs.pact.io

We use Pact for contract testing https://docs.pact.io/

The introduction here is quite good: https://docs.pact.io/

Pact.Net documentation: https://docs.pact.io/ Mountebank documentation: http://www.mbtest.org/ The Microsoft.AspNetCore.TestHost package on GitHub: https://github.com/aspnet/AspNetCore/tree/main/src/Testing/Microsoft.AspNetCore.TestHost

There's also https://docs.pact.io/ but I haven't had time yet to really look into it but probably someone else can tell something about it.

This PoC shows a step by step implementation of contract testing using Pact.

Contract tests assert that inter-application messages conform to a shared understanding documented in a contract. Without contract testing, the only way to ensure that applications will work correctly together is by using expensive and brittle integration tests.

If you are updating your API based on user feedback, you can work with your team or stakeholders to build an API contract describing how your API should function. You can use JSON schemas to document your API’s endpoint response codes and set up the contract. The contract must be accepted by all parties. Then, any changes made to the API must pass the contract test before being approved. Contract testing can be automated and incorporated into your CI/CD pipeline. Contract testing tools include Pact and Spring Cloud Contract.

Pact.

I have contract tests (https://docs.pact.io/) to ensure the integration works.