SilkTest User's Guide: Running Tests - Using the results file to find errors

<< Running Tests - Multiple sets of results | Running Tests - Navigating to errors in the testplan >>

Running Tests - Using the results file to find errors

<< Running Tests - Multiple sets of results | Running Tests - Navigating to errors in the testplan >>

152

User's Guide

6 R

UNNING

ESTS

AND

NTERPRETING

ESULTS

Using the results file to find errors

Using the results file to find errors

You can expand the text of an error message yourself or have SilkTest find the
error messages for you.

Clicking on the red
plus sign

Procedure To expand an error message to reveal the cause of an error, click
on the red plus sign preceding the message. In addition, you see the call
stack, which is the list of 4Test functions executing at the time the error
occurred.

In the following example of a results file, the error occurred in VerifySelText,
which was called from Case_Back_Char on line 39 of find.t.

Using Find Error

Procedure To find and expand the next error or warning message in the
results file, select Edit/Find Error.

Tip To skip warning messages and find error messages only,
deselect Find Error Stops at Warnings check box in the Runtime
Options dialog.

You can also use the Find, Find Next, and Go to Line commands on the Edit
menu to navigate through a results file.

Navigating to errors
in the script

SilkTest provides several ways to move from the results file to the actual error
in the script:

Double-click in the margin next to an error line to go to the script file that
contains the 4Test statement that failed.

Click on an error message and select Results/Goto Source.