VTerminal VS Testcontainers

You could check out my name generation library and another library that I wrote to give Swing a terminal Look-and-Feel

This is one of my projects which is set up with JitPack and Maven. I can include it in any other project by adding it as a dependency to that project's Maven pom.xml file.

VTerminal - A new Swing LaF which allows for a grid-based display of Unicode characters with custom fore/background colors, font sizes, and pseudo-shaders.

VTerminal

The library is VTerminal. The master branch contains all of the older AWT-based code and the 2020.11 branch contains all of the newer Swing-based code. Although it's mostly done and working, I'm holding off pushing the full rewrite in 2020.11 to master until I can get more documentation written for it.

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?