Choosing a Breakpoint Type - WinRunner

WinRunner enables you to set two types of breakpoints: Break at Location and Break in Function.

Break at Location

A Break at Location breakpoint stops a test at a specified line number in a test script. This type of breakpoint is defined by a test name and a test script line number. The breakpoint marker appears in the left margin of the test script, next to the specified line. A Break at Location breakpoint might, for example, appear in the Breakpoints List pane as:

ui_test[137] : 0

This means that the breakpoint marker appears in the test named ui_test at line 137. The number after the colon represents the pass count, which is set here to zero (the default). This means that WinRunner will stop running the test every time it passes the breakpoint.

Break in Function

A Break in Function breakpoint stops a test when it calls a specified userdefined function in a loaded compiled module. This type of breakpoint is defined by the name of a user-defined function and the name of the compiled module in which the function is located. When you define a Break in Function breakpoint, the breakpoint marker appears in the left margin of the WinRunner window, next to the first line of the function. WinRunner halts the test run each time the specified function is called. A Break in Function breakpoint might appear in the Breakpoints List pane as:

ui_func [ui_test : 25] : 10

This indicates that a breakpoint has been defined for the line containing the ui_func function, in the ui_test compiled module: in this case line 25. The pass count is set to 10, meaning that WinRunner stops the test each time the function has been called ten times.