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

What should I check if when running SilkTest scripts via SilkCentral Test Manager, compile errors are returned in the results file(s)?

What should I check if when running SilkTest scripts via SilkCentral Test Manager, compile errors are returned in the results file(s)?

Problem:

What should I check if when running SilkTest scripts via SilkCentral Test Manager, compile errors are returned in the results file(s)?

Resolution:

QUESTION
----------------------------------

What should I check if when running SilkTest scripts via SilkCentral Test Manager, compile errors are returned in the results file(s)?

ANSWER
----------------------------------

If you are generating compile errors when you run your SilkTest script through SilkCentral Test Manager but not when the same script runs in SilkTest in a project or with a particular Options Set, then please check the steps below.

Before you start, make sure that you can run your scripts in SilkTest without having the project open. When everything is working perfectly, then go to Options/Save New Options Set... and save an options set to later use in SilkCentral Test Manager.

  1. Firstly, make sure that you that you have assigned an Options Set to the test definition that you are executing, see below.

    (For more information on creating/saving Options Sets please see SilkTest help.)

  2. In order to be able to browse to the Options Set as in the above image, you must make sure that you have saved the Options Set to the same folder as the script file that you have already assigned to this test definition. This folder is specified in the UNC path on the Source Control Profile. You can view the Source Control Profile that you have assigned to this test definition by clicking on the properties tab of the test container that contains this test definition; see the below screen shots.

  3. Your Option Set must reference the frame file needed for the script to execute. This frame file must also be saved to the same folder as the Option Set and script file. The path to the frame file, as in the image below, needs to be the absolute path to the working folder on your execution server (the working folder is specified in your Source Control profile). Otherwise the frame file will not be found and you will most likely see compile errors in the results files that are saved to SCTM.

Old KB# 24725

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 19:48
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.