background image
<< Running Tests - Fixing errors in a script | Running Tests - To store results in unstructured ASCII format >>
Running Tests - Managing results file information
<< Running Tests - Fixing errors in a script | Running Tests - To store results in unstructured ASCII format >>
156
User's Guide
6 R
UNNING
T
ESTS
AND
I
NTERPRETING
R
ESULTS
Managing results file information
Debugging tools
You might need to use the debugger to explore and fix errors in your script. In
the debugger, you can use the special commands available on the Breakpoint,
Debug, and View menus.
For more information, see Chapter 7, "Using the Debugger".
Marking failed
testcases
When a testplan results file shows testcase failures, you might choose to fix
and then rerun them one at a time. You might also choose to rerun the failed
testcases at a slower pace, without debugging them, simply to watch their
execution more carefully.
Procedure To have QA Organizer identify the failed testcases, select
Results/Mark Failures in Plan when the results file is active.
QA Organizer marks all the failed testcases and makes the testplan the
active file.
Managing results file information
You can:
·
Store the results in an unstructured ASCII text file for printing or viewing
·
Export the results to a structured file for further processing
·
Send the results to QA Radar for further processing
·
Merge two testplan results files
·
Compare two different testplan results files
·
Generate a Pass/Fail report from a testplan results file
·
Compact a results file
Storing results in an unstructured ASCII format
As a QA engineer, you might need to prepare a status report based on one or
more sets of results or you might want to print the errors you found after a
day of testing. SilkTest allows you to extract the information you want in an
unstructured ASCII text format and send it to a printer, store it in a file, or
look at it in an editor window.
Note To learn how to save your results in a structured text file that
an application such as a spreadsheet can process, see the next
section.