TestNG VS JUnit

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.

Because I only wanna use the cmd java test, so I chose Junit4 which supports Plain-old JAR. I did test according to the Getting started document. But when I ran the javac -cp .:junit-4.XX.jar:hamcrest-core-1.3.jar CalculatorTest.java I got the error message CalculatorTest.java:4: error: package main does not exits. I tried to reorganize the folder and set Path according to others' experience 1, 2, but it still did not work.

Oops, another error. This is why we should read the manual 😅.

JUnit4

Delete those imports and remove the junit-jupiter-api dependency. Follow the instructions for JUnit 4.

Quite a lot of Java dependencies bring Junit 4 or Junit vintage engine as a transitive dependency.

The AHTest039.json file is the actual test. My testRunner() method (no relation to JUnit test runners) reads that JSON file, processes it, and asserts that the test passed. So my test class consists of a few Java methods, and what is essentially a list of JSON files to process.