The OpenFastTrace IntelliJ Plugin 0.8.0 is out. While version 0.7.0 made OFT runs configurable, this release focuses on how you interact with the results.

# Test Runner UI Integration

The most significant change is that OpenFastTrace results now integrate directly with IntelliJ’s built-in Test Runner UI. Instead of scanning a text report, you get a structured tree of results.

This integration provides several benefits:

• Visual Feedback: Results are grouped by source file, specification item, and trace link. Clean items show as passed, while defects appear as failures.
• Deep Inspection: You can expand source files to see affected items and inspect incoming/outgoing trace links as sub-tests.
• Contextual Information: Item IDs, link status, and defect explanations are visible in the test details.
• Easy Navigation: You can jump from result nodes directly to the source files, specification declarations, or coverage tags.

The global Tools | OpenFastTrace | Trace Project action and new run configurations use this UI by default. If you prefer the raw report, you can still opt into the plain text output in the run configuration.

We are pleased to announce the release of OpenFastTrace 4.5.0. This release is particularly special as it marks the 10th anniversary of OpenFastTrace on GitHub.

# New Mastodon Presence

As part of our community outreach, OpenFastTrace is now on Mastodon. You can follow us for updates and discussions at @OpenFastTrace@mastodon.social.

# CLI Improvements

The command-line interface has been improved with standard help options. You can now use -h or --help to display usage information. Additionally, the help message now includes the version of OpenFastTrace, making it easier to verify the environment you are running in.

2026 marks a special milestone for OpenFastTrace: it has been a bit more than 10 years since the first commit was pushed to GitHub!

While OFT as we know it today started in 2016, its roots go back much further. The journey began in 2003 with a tool called ‘ReqMgr’ at 3SOfT GmbH. Over the years, it evolved through various iterations—ReqMgrNG, ReqM2, and Allosaurus—driven by the needs of the automotive industry for reliable requirement tracing.

Two things happened recently that I think are worth mentioning: OFT got an IntelliJ plugin, and we added several skill files for AI coding agents.

# The IntelliJ Plugin

Running OFT during development should be as seamless as possible. While we have had build integration for a long time via our Maven and Gradle plugins, many developers still found themselves dropping to the command line to check tracing results. That is fine for a final check before a commit, but during active development, it can interrupt your flow.

Our next goal is to get OFT packaged for easier installation. We will start with Debian and RPM packages soon. Ultimately, we would like to get OFT shipped with the popular distributions. This will probably help with the adoption. But until that happens, it will be a long way.

By the way, if you read this and are a curious developer with experience in the Apple ecosystem, we are looking for help with packaging OFT for macOS. If you are interested, please reach out to us.