cheng/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add some tips on fault navigation after input from Phlip

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@33984 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Michael Wetherell 2005-05-08 16:16:34 +00:00
parent ad44b2c7ff
commit 51c432b77a
1 changed files with 20 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/tech/tn0017.txt
View File

@ -69,6 +69,25 @@ III. Running the tests
or to list the tests:
test -L MBConvTestCase
5. Fault navigation.
VC++ users can run the programs as a post build step (Projects/Settings/
Post-build step) to see the test results in an IDE window. This allows
errors to be jumped to in the same way as for compiler errors, for
example by pressing F4 or highlighting the error and pressing return.
Similarly for makefile users: makefiles can be modified to execute the
test programs as a final step. Then you can navigate to any errors in the
same way as for compiler errors, if your editor supports that.
Another alternative is to run the tests manually, redirecting the output
to a file. Then use your editor to jump to any failures. Using Vim, for
example, ':cf test.log' would take you to the first error in test.log, and
':cn' to the next.
If you would like to set a breakpoint on a failing test using a debugger,
put the breakpoint on the function 'CppUnit::Asserter::fail()'. This will
stop on each failing test.
IV. Notes
---------
@ -100,5 +119,5 @@ IV. Notes
=== EOF ===
Author: VZ
Author: VZ & MW
Version: $Id$