Revit Testrunner

I’m thrilled to share some exciting news from my recent open-source journey. I’ve made a significant contribution to the Revit.TestRunner project, an Addin for Autodesk Revit, by updating it to .NET 8 and Revit 2025. Check it out here: https://github.com/beyerl/Revit.TestRunner2025

What is Autodesk Revit?

For those who may not be familiar, Autodesk Revit is a powerful Building Information Modeling (BIM) software developed by Autodesk. It’s extensively used by architects, engineers, contractors, and designers to create, manage, and visualize building designs and construction projects. Revit’s comprehensive tools and features make it a staple in the AEC (Architecture, Engineering, and Construction) industry.

What is Revit.TestRunner?

Revit.TestRunner is a straightforward Addin designed for Autodesk Revit. It enables the execution of unit tests from a specified test assembly, leveraging references to the Revit API. The test framework in use is NUnit v3, a popular unit-testing framework for all .NET languages.

The Need for an Update

Revit.TestRunner had not been updated to support .NET 8 and Revit 2025, which posed a challenge for developers working with the latest versions of Revit. Recognizing this gap, I decided to step in and update the project myself. You can check out my updated version here: Revit.TestRunner2025.

The Update Process

In my fork of Revit.TestRunner, I focused on updating all projects to .NET 8. Given the goal of simplicity, I did not prioritize backward compatibility. As a result, my fork is designed to work exclusively with Revit 2025 and does not support older versions.

Here are some key points about my update:

  • .NET 8 Upgrade: I updated all projects within the Revit.TestRunner solution to .NET 8, ensuring they are compatible with the latest Revit 2025.
  • Commandline Convenience: I made the Revit folder configurable via commandline arguments. This added flexibility makes it easier for users to specify their Revit installation path.
  • Debug Mode Fixes: I also removed the automatic override of arguments in debug mode, streamlining the debugging process.

Future Directions

I anticipate that Tobias Flöscher, the original repository owner, might aim for a backward-compatible solution. Given this, merging my fork as it stands might not be ideal. However, I hope that my contribution will assist in addressing some of the issues that arise from upgrading from .NET Framework 4.8 to .NET 8.

Conclusion

This contribution has been an exciting and fulfilling experience. By updating Revit.TestRunner to .NET 8 and Revit 2025, I hope to have made a valuable addition to the community and to those working with the latest versions of Autodesk Revit. If you’re working with Revit 2025, feel free to explore my fork and see how it can benefit your workflow.