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.