Siebel Test Automation Module configuration

OpenText Functional Testing support for Siebel applications is based on the Siebel Test Automation API (SiebelAx_Test_Automation_18306.exe). Before you can create or run tests or business components on your Siebel application, you must modify the Siebel Test Automation module configuration and instruct your Siebel application to generate test automation information.

To test your Siebel application using the Siebel Add-in, confirm that your Siebel server has the Siebel Test Automation module installed and correctly configured to perform test automation. For detailed information, see the section that describes how to set up your functional testing environment in your Siebel documentation, provided with your Siebel installation.

In this topic:

Enabling OpenText Functional Testing to create tests

You must instruct the Siebel Web Engine (SWE) to generate test automation information for the Siebel application, using a SWE command.

To do so, append the SWECmd=AutoOn token to the URL of your Siebel server. For example: http://hostname/callcenter/start.swe?SWECmd=AutoOn. If you do not append this token, the SWE does not generate test automation information.

If you select the Open the following application when a record or run session begins option in the Siebel Tab (Record and Run Settings Dialog Box), OpenText Functional Testing automatically appends the Siebel Test Automation information to the URL (you do not need to specify it manually in the URL).

As you record a test or business component on your Siebel application, OpenText Functional Testing records the operations you perform. OpenText Functional Testing works directly with the Siebel Test Automation API (SiebelAx_Test_Automation_18306.exe) to record your operations. Therefore, although OpenText Functional Testing records a step for each operation you perform, it adds the steps to your test or business component only when API events are sent to OpenText Functional Testing (when information is sent to the Siebel server).

When test automation is activated on a Siebel server and requested in the URL, the Siebel Web Engine (SWE) generates additional information about each object in the Siebel application when constructing the Web page. Each object has a specific set of properties, events, and methods that provide functionality for the Siebel application. The Siebel Test Automation API maps to these objects to enable you to manipulate your Siebel application from OpenText Functional Testing when recording and running tests or business components on the Siebel application.

Back to top

Passwords for the Siebel application

If a password for generating test automation information is defined on your Siebel Server, you must also indicate that password in the URL (in addition to the SWECommand=AutoOn token described above). The URL token is in the format AutoToken=password. For example: http://hostname/callcenter/start.swe?SWECmd=AutoOn&AutoToken=mYPass. This enables OpenText Functional Testing to run the Siebel Test Automation API SiebelAx_Test_Automation_18306.exe even in secure mode.

If a password is defined for the Siebel Server and you do not append this token to the URL, the SWE does not generate test automation information.

For details on whether your Siebel Server is secured for test automation, contact your Siebel system administrator.

If you select the Open the following application when a record or run session begins option in the Siebel Tab (Record and Run Settings Dialog Box), click the Advanced button, and specify the password in the Siebel automation access code box in the Advanced Siebel Record and Run Settings dialog box, OpenText Functional Testing automatically appends the password information to the URL (you do not need to specify it manually in the URL). For details on the Record and Run Settings dialog box options, see Environment variables for Siebel applications.

Back to top