DUnit extension: Show in IDE

Find the location of your testmethod or failure with one double click.

About: Show in IDE

Currently when you are using the DUnit GUI Test Runner, and something goes wrong in a method, you have to locate that method in the Delphi IDE manually. Which means thinking real hard in what unit that method was, and then finding the source that now suddenly failed. With the Show in IDE extension you can use one double click to find the location! The only thing you need, besides this extension, is ModelMaker code explorer version 6.0 (or higher). If you don't know that tool yet, then now it is time to find out, but be warned, when you start using it you will be addicted and can't live without it anymore...

How it works

There are 2 ways in which the Show in IDE DUnit extension can work. The simple "it just works" way and the enhanced ways.

The simple way is as simple as:

• Use GuiTestRunnerEx(.pas) instead of the standard GuiTestRunner
• Now you can just doubleclick the methods in the GuiTestRunner and ModelMaker code explorer will locate them for you in the IDE. But only if the code explorer has 'seen' the units before (when you have navigated to them once within the IDE)

The enhanced way is a litle more complicated:

• Follow the the simple way above.
• But also compile DUnit with jclDebug support (so download the JCL, and compile DUnit with USE_JEDI_JCL defined)
• Make sure your DUnit exe has meta data jclDebug can use (like a .map file, see jclDebug manual)
• Implement ITestIsTestCase in your test case, (it's just one method, with one line: Result := Self;) and add DUnitShowInIdeServices to your uses clause
• Now you can doubleclick any test method! Even if the code explorer hasn't seen it before (since the unitname is now known)
• In case of failures hapening in your unit tests, you can just double click it in the Failure list to jump to the line that caused the failure (for example the line containing
  the check/assert method)
  

The whole extension just consists of the 2 units that are above mentioned: GuiTestRunnerEx.pas and DUnitShowInIDEServices.pas So extract them from the download and put them somewhere where Delphi can find them!

But a screenshot might say more then a thousand words: this is after double clicking the failure in DUnit. The source code editor navigated to the correct line (see the > cursor indicator, another a ModelMaker Code Explorer feature.)