After installing FinalBuilder for the first time, I looked through the list of actions to see what 3rd party tools were supported. I was pleasantly surprised to see an action for every tool I use in software development except one, DUnit. I thought this was odd but I soon realized that DUnit is supported, just not as a custom action.
Follow these steps to use DUnit in FinalBuilder:
1) Add a Compile Delphi Win32 Project action to your FinalBuilder project.
2) Point the Compile Delphi action to your DUnit project and configure it as needed to compile the project.
3) Add an Execute Program action to the FinalBuilder project. This action is found under the Windows OS action group.
4) Point the action to the compiled bits from the Compile Delphi action. In other words, point it to your DUnit program.
5) Mark the Log Output option, which should be marked by default.
That’s it. FinalBuilder will run your DUnit unit tests as part of the build process and the output from the tests will be captured by FinalBuilder. And of course you can configure the FinalBuilder project to act accordingly based on the pass/fail result of your unit tests.
Some people might think FinalBuilder should have a custom action for DUnit. However, the action would only be a direct copy of the Execute Program action. Or maybe it would combine the Compile Delphi and Execute Program actions into a single action. But as you can see a custom action is not needed. DUnit unit tests are support through the Execute Program action and a custom action specific to DUnit would just be a waste of time for the folks at Vsoft Technologies. Their time is better spent adding support for more tools and adding more features to an already great product,
- Delphi (BDS) Live Templates for SQL Server
- Delphi 2006 Survey
- Namespaces in Delphi
- Parse CSV or Tab Separated Files Using Delphi
- wpsCsvParser Fix
- CSV Parser for Delphi
- Video Tutorials for Delphi
- FREE 3rd Party Tool bundle with BDS 2006
- From Delphi to C# and Back Again