Comments on: DUnit tricks: Getting stack traces for test failures

By: Ajasja

Ajasja — Fri, 25 Apr 2008 14:44:44 +0000

I did find a partial solution:
I use SendKeys (http://delphi.about.com/od/adptips2004/a/bltip1104_3.htm) to activate delphi and send CTRL+F12 (view unit) and then the unit name + ENTER.

So the unit has to be part of the project, but otherwise it works quite nicely. I did have some problems with the editor losing focus, but the new version of DDevExtension (http://andy.jgknet.de/dspeedup/index.php?page=DDevExtensions) solves that. I do have the unit selector turned of though.
Not the most elegant, but it works

Here’s the code extract:
var
DelphiHandle : hwnd;

DelphiHandle:=FindWindow(’TAppBuilder’,nil);
AppActivate(DelphiHandle);
SendKeys(’^{F12}’,true); //Ctrl+F12 is View Unit
SendKeys(Pchar(aUnitName),true); //look up unit name
SendKeys(’~',true); //enter

SendKeys(Pchar(’%g’),true); //Alt+G is the goto line dialog
SendKeys(Pchar(IntTostr(aLineNum)),true); //send line
SendKeys(’~',true); //enter

By: Joe

Joe — Tue, 22 Apr 2008 12:17:03 +0000

No, there doesn’t seem to be a way to do that. Even if I compile with TD32 debug info, which is supposed to have even more info than the detailed .MAP file, I don’t get file paths in the stack trace. And if those paths were in the TD32 debug info, I’m pretty sure the JCL would be able to extract them.

You’ll probably have to keep a list of directories to search through. There doesn’t seem to be any better way.

By: Ajasja

Ajasja — Thu, 17 Apr 2008 11:41:41 +0000

Is it possible to get the full file name (file name + path) in the stack trace?
It would be really nice, if one could just double click the failures and be taken to the exact line in the Delphi IDE.
I’d like to add this to the TGUIRunner, but I just can’t get the full file path.

Best regards,
Ajasja