How can SilkTest testcases run on Windows 9.x when SilkCentral Test Manager Execution Servers do not work on these platforms?

0 Likes

Problem:

How can SilkTest testcases run on Windows 9.x when SilkCentral Test Manager Execution Servers do not work on these platforms?

Resolution:

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

How can SilkTest testcases run on Windows 9.x when SilkCentral Test Manager Execution Servers do not work on these platforms?

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

Testing requires that I must run SilkTest testcases on Window 9.x (95,98 and ME) but the documentation states that these are not supported platforms for a SilkCentral Test Manager Execution Server.


N.B. Linux and Unix Agents are not currently supported by SilkTest (as of June 2005) but support for these is planned and the methods described below will apply.


You will need to use the ability of SilkTest to run testcases on remote machines. You will require two machines, a SilkCentral Test Manager compatible Execution Server (NT,XP,2000 ...) and the remote machine with the Application installed and a running and network enabled SilkTest Agent.

In this case you can define the location of the SilkTest agent (SilkTest AUT (Application Under Test) Hostname).

Procedure To add/edit a SilkTest AUT host to the selected execution definition:

  1. From the Execution unit (Execution View), select the execution definition for which you would like to assign the SilkTest AUT host.

  2. Select the Deployment tab.

  3. Click the lower Edit button (in the SilkTest AUT Hostname portion of the GUI).

  4. The Edit SilkTest AUT Hostname dialog appears. In the Hostname field, type the name of the computer where the SilkTest agent runs. Proper configuration of option files is required here. See SilkTest documentation regarding the commandline option -m for details.

  5. Click the OK button to add the SilkTest AUT host to the selected execution definition.


Note. The remote Agent must be started on the AUT host. The Execution Server cannot start remote Agents on the AUT host.

Old KB# 24832
Comment List
Related
Recommended