3.0

This release fixes bugs in the Kotlin libraries and the Java wrapper for Memoir. It also implements some robustness improvements to Change Scan. On the Java side, there is now a JUnit integrated version of the Java wrapper for Memoir, meaning that Memoir now plays nice with JUnit. An example module will be included in the IntelliJ project. An example of using Memoir with JUnit in Eclipse will be included as part of the release.

Testing was done against Linux Mint 21.1, macOS Monterey, and Windows 11.

2.1

Release 2.1
On the Kotlin side not much has changed, save for updates to the latest version of Kotlin, efforts to cull down the number of warnings, and efforts to increase the documentation comments. Source code is now included in all JAR files to provide for better "intellisense" completions.

The big news for this release are Java wrappers for Memoir, Toolbox and Koarse Grind. For those who haven't noticed, trying to use Kotlin from Java can sometimes get... er... messy. --Much more so than the other way around, using Java from Kotlin. I'd actually had hopes to be able to use these projects from Java when I first created them, so for this release I decided to focus on making that happen. I've taken the time to produce full Java wrappers for all of Memoir and Toolbox. Some parts of Koarse Grind, and all of the "Descriptions" module, have been left as unwrapped Kotlin since it is usable as it is. New examples for the Java bits have been provided, and some testing in Java was also done with the Eclipse IDE.

Testing was done against Linux Mint 21.1 and Windows 11.

2.0

Release 2.0

Primary changes to this release are a new paradigm for Koarse Grind. Refer to the Koarse Grind Example module.

• The concept of declaring several "Categories" each test might fit into is now abolished.
• What was previously the "TestCollection" class now serves as each test's category. That class is now internal and renamed "TestCategory".
• All tests now declare a "CategoryPath" delimited by the pipe character ( | ). This path determines how the tests are organized in the test log.
• Example: "External API|Add Content|Negative Tests".
• Outfitters also declare a CategoryPath which determine the specific category they setup/cleanup.
• TestFactories no longer determine the name of the collection/category that the tests go in. The test programmer specifies this for each test.
• The root output folder can be changed from $/Documents/TestResults to the directory of your choice by setting defaultParentFolder before calling TestProgram.run().
• Manually creating a "TestCollection" (now TestCategory) and populating it with tests is now prohibited. Use the CategoryPath field instead.
• This release of Koarse Grind is verified to work on Windows 11, macOS Ventura, and Linux Mint 21.1.

1.0

I've applied bug fixes, made improvements, and plugged feature gaps as I discovered them over the past several months. Time to call this officially a "One-Point-Oh," and no longer a pre-release or beta!