Testcontainers VS TestNG

There are a handful of ways to start Testcontainers, including JUnit4 annotations, JUnit5 annotations, ApplicationContextInitializer, JDBC URL scheme, and manual container lifecycle control. Let's choose manual control for now as the least "magic" option:

Repository

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.

However, you must note that over-parallelization can cause resource contention and performance issues, so monitor it. Use tools like pytest-monitor, TestNG, and Appium to find your optimal parallel execution configuration.

Inspired by JUnit, TestNG offers advanced features for complex, large-scale testing scenarios, covering unit, functional, integration, and end-to-end tests.

If you’re interested in learning more about TestNG, visit its official website for additional information.

### TestNG

Introduction: TestNG is a versatile testing framework that accommodates various testing needs, including unit, functional, and integration testing. It's particularly useful for Java developers looking for a comprehensive solution.

Testing tools on the JVM stopped using reflection about twenty years ago, they all use annotations these days (e.g. https://testng.org, https://junit.org). Rust has annotations too, obviously.

Recently though we've run across a few issues with the asserts in TestNG. In 7.3.0, some changes broke assertSame/assertNotSame that also broke some of our tests. This was partially fixed in 7.4.0, but some overloads of assertEquals were still broken. This is fixed, but I don't think the fix has been delivered in a release yet. Further investigation revealed that at least one overload of assertNotEquals has been broken, apparently since 6.9.5 or even earlier.

TestNg DTD W3 Schools Liquid Technologies

TestNG is a Java-based open-source testing framework. The framework is inspired by JUnit and NUnit. You can also create an HTML report during testing implementation.