Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why does Results - Go to Source take me to the script file instead of the frame file in SilkTest?

Why does Results - Go to Source take me to the script file instead of the frame file in SilkTest?

This behaviour can occur if you are using relative paths in your use statements. Due to this, errors are reported in a frame file that has no path in the results file. Then when double-clicking on the results file or going to Results - Go to Source, SilkTest will look in the same directory as the script file. As the frame does not exist there, SilkTest will then open the script file and highlight the function. In order to get the frame file to open when double clicking the results files or using Results - Go to Source, you need to implement one of the following frameworks:

  • Have the frame files in the same directory as the script files
  • Have a full path to the frame file defined in the use statement
  • Place the frame file directory in the use path in the Runtime Options.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 20:38
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.