Results-Silk test

Results
Opening Results Files : Selecting Results : Results To Store : Merging Results : Deleting Results : Exporting Results : Orphaned Tests
SilkTest stores results files in a proprietary format. You cannot view a results file with a normal ASCII viewer, such as notepad. By default, there are five (5) results stored in a single results file, although you can change this setting. Each one of your result slots is utilized, and as you run the plan each time, the oldest result is deleted.
Opening Results Files
To open a results file, change the FileType in the Open dialog to *.res files.
Selecting Results
To view a specific set of results, open the results file, then choose Results -> Select from the SilkTest menu.
This image shows the Select Results dialog, which is used to select the specific result to display from the current results file. This dialog is invoked using Results -> Select.
Results to Store
In the image above, the default number of results to store has been changed to eight (8).
Merging Results
You may want to merge two results into a single result. This may happen if you have to abort a test run partway through. You can run the unfinished tests later, then use Results -> Merge to merge the current result with an earlier result.
This image shows the Merge Results dialog. You may select any of the previous results to merge with the current result.
Deleting Results
You may reserve the results slots your have specified by using Results -> Delete to remove results files which you no longer need.
This image shows the Delete Results dialog. You may select one or more results to delete.
Exporting Results
You may export results for analysis with a spreadsheet, database or other program. Use the Results -> Export menu to invoke this dialog. You may specify what to extract, what separator to use, and the output file.
This image shows the Export Results dialog. You may specify exactly what to export.
Orphaned Tests
This situation occurs when the results file cannot find the testplan (.pln) file which was originally executed. The remedy is to place the testplan (.pln) file in its original location.