Today we released OpenFastTrace 2.2.0. As the main new feature the HTML report now shows a trace summary and a small table-of-contents. Additionally, we focused the README on GitHub on OFT users rather than developers and move the developer topics to the new developer guide.

Today I want to thank the author of recoverjpg, Samuel Tardieu. This tool is proof that “do one thing, do it well” results in the most useful software. A family member brought an SD card back from a vacation trip abroad and the filesystem broke when she plugged the card into her Mac. Needless to say that this is not the usual scenario, because many times before everything went well.

After releasing OpenFastTrace 2.1.0 it was high time to release the corresponding Gradle plugin in version 0.5.0. This is a drop-in update, just update the version number and benefit from the features and bugfixes of OFT 2.1.0. During the release process we also fixed the sonar analysis and some sonar warnings. We also used the opportunity to document (and test) two features that where already implemented but not described: Import requirements from a maven repository

After two bugfix releases a new feature release. On November 19th Christoph create the Release for OpenFastTrace 2.1.0. Feature-wise we are happy to announce an improved HTML report. Sonar checks are now up and running again and the last JavaDoc errors have been rooted out. We also fixed the deep coverage detection which was pointing upwards instead of downwards in the tracing chain. As a consequence we had to rework link loop detection, which acts a lot smarter now than before.

In a recent blog post I wrote about the migration from JUnit4 to JUnit5 as unit testing framework. Even though the version number increase from 2.0.1 to 2.0.2 might not look like much, it is in fact a major milestone for OpenFastTrace, since from here on writing tests will be faster and more efficient.