junit5 VS eo-yaml

To make the above check work we need to wrap it in JUnit test:

Java / JUnit

Next, you need to install a testing framework that will be used for performing unit testing in your project. Several testing frameworks are available depending on the programming language used to create an application. For example, JUnit is commonly used for Java apps, pytest for Python apps, NUnit for .NET apps, Jest for JavaScript apps, and so on. We’ll use the Jest framework for this tutorial since we are using JavaScript.

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.

To get started with testing, search for a popular testing framework for your programming language. PHP has PHPUnit, for example. Java has JUnit. Flutter apps use Flutter Driver. No matter your language or framework, there is a testing framework that will work for your app.

Another library which may be of use to you once you've gotten to grips with the basics of Java is JUnit. JUnit provides functionality for unit testing, allowing you to more easily see if your code is working as expected/if you've accidentally broken anything, via letting you write tests that can check if your code is behaving as expected or not.

Official Website : https://junit.org/

In my last episode (https://youtu.be/cs2Wu9Co-2s) I said that we shouldn't use JUnit @BeforeEach to setUp test fields. Christoph Sturm (https://twitter.com/globalo) pointed out that there is an, erm, feature of JUnit 5 that means that we sometimes have to use @BeforeEach methods to initialise resources if we want them to be released in @AfterEach. The bug report is here https://github.com/junit-team/junit5/issues/1358 With or without this feature, we probably should use @BeforeEach to run code that will allocate non-memory resources that we need to free in @AfterEach, if only for symmetry. I suppose that also applies to any side-effects that we need to be reverted and that are not confined to the state of the test fixture.

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.

Testcontainers is a Java library that supports JUnit tests providing lightweight instances of anything that we can run in a Docker container.

eo-yaml is primarily a YAML builder/reader in the generic sense (you can build/read YamlMapping or YamlSequence etc), inspired by JSON-P. eo-yaml also supports mapping a Java Bean to YAML (the reverse is not yet supported, if I remember well). Everything is explained in detail in the wiki. Also the README offers a good overview.

github.com/decorators-squad/eo-yaml