Debugging Tests
Debugging
is the process of eliminating bugs (or errors) in our code. Here we are
not trying to find the errors in the AUT (Application Under Test) but
in our script. The WinRunner Environment provides us with some
facilities to easily debug the test scripts. These can be divided into
three categories:
1. Stepping commands
2. Breakpoints
3. Watches
Stepping Commands
These
commands allow you to execute script slowly line by line or by block.
These are particularly useful when the code consists of decision
structures and looping structures and you want to see the flow of
logic. The different step commands can be accessed through the Run menu
or by using the corresponding softkeys. The different step commands are:
Step: When this command is issued only the current line pointed by the yellow pointer is executed. The softkey is F6.
Step into: When
this is issued it also executes the current line of code only. But if
the current line of code calls a function or another test then it is
code flow shows the other procedure or test and executes that line by
line.
Step out: This is
generally used in conjunction with step in. This command completes the
call to the function or test and comes out and continues with next
statement.
Step to cursor:
This is used to execute a block of script. To run a block of script, go
to the first line and click set the yellow pointer on that line then
move the text insertion cursor to the last line in the block and select
Run=> Step to cursor.
|