background image
<< Running Tests - Bitmap tool | Running Tests - Managing results file information >>
Running Tests - Fixing errors in a script
<< Running Tests - Bitmap tool | Running Tests - Managing results file information >>
User's Guide
155
6 R
UNNING
T
ESTS
AND
I
NTERPRETING
R
ESULTS
Fixing errors in a script
figure below; however, in reviewing the text, you can see, for example, that
SilkTest expects the Case Sensitive check box to be unchecked (FALSE),
while the actual value found during testcase execution was checked (TRUE).
When you have more than one screen of values or are using a black-and-
white monitor, use Results/Next Result Difference to find the next difference.
Use Update Expected Values, described next, to resolve the differences.
Fixing errors in a script
Updating expected
values
You might notice upon inspecting the Difference Viewer or an error message
in a results file that the expected values are not correct. For example, when
the caption of a dialog changes and you forget to update a script that verifies
that caption, SilkTest will log errors when you run the testcase. To have your
testcase run cleanly the next time, you can modify the expected values with
the Update Expected Value command. Note that this command updates data
within a testcase, not data passed in from the testplan. (For more information
on testplan data, see Chapter 10, "Adding Data to a Testplan".)
Procedure To fix incorrect values in a script:
1
Make the results file active.
2
Select Results/Update Expected Value.
SilkTest replaces the expected values in the script with the actual values
found at runtime.
3
Optionally, select Run/Testcase in order to run the test and confirm that it
now passes.