
11 Dec
2007
11 Dec
'07
6:32 a.m.
"Neil Groves" <neil@grovescomputing.com> wrote in message news:000001c83a7b$7a2ac1b0$6e804510$@com...
Hi Thorsten,
I normally place soft breakpoint in the code that announces the test failure and walk the call stack.
Alternatively you can use the IsDebuggerPresent() call combined with DebugBreak as a Windows only modification to the assertions. This only causes a debug break if a developer has attached a local debugger. The automated unit test execution is unaffected.
See: http://msdn2.microsoft.com/en-us/library/ms680345.aspx for IsDebuggerPresent()
This is what bost.Test doing already. Gennadiy