1. Testing Business Applications Guide
  2. Importing the Test Scripts

Importing the Test Scripts

You can follow the procedures in this topic to do the following:

  • Activate the workflow for importing test scripts.

  • Import the generated test scripts from the Script Pane to the database.

  • Import the generated test scripts from the Release screen to the database.

Activating the Workflow for Importing Test Scripts

To activate the workflow for importing test scripts, make sure the Workflow Process named Testscript Import Workflow is active. See Siebel Business Process Framework: Workflow Guide to activate it.

Importing the test scripts from Script Pane to Database

To import the test scripts from the Script Pane to the database:

  1. Click the Camcorder icon on the toolbar, then the script button.

  2. Select the scripts to be imported from the Script pane.

    You can choose to select a single script or multiple scripts to import them into the database.

  3. Click Import.

    A pop up message is displayed with the number of scripts that were imported successfully and the scripts that were not imported successfully.

    Note: The import process will fail when you try to import a script with the same name if it is already available in the database. The log details of a failed import process will be available in the Siebel Logs folder.

Importing test scripts from Release Screen to Database

To import the test scripts from the Release screen to the database:

  1. Navigate to the Sitemap, Release screen, then the Test Scripts view

  2. Query for the test script to be exported.

  3. Click Export.

    The test script is downloaded, in xml format, to the download folder.

    Use this xml file to import a test script into the database.

  4. Navigate to the Sitemap, Release screen, then the Test Scripts view.

  5. In the Test Scripts list applet, click Import.

  6. In the File Upload popup window that appears, select the xml file to be imported.

  7. Click Load.

The script will be imported into the database. If you have a script with the same name in the database, it will be replaced with the existing script. In this way the scripts can be exported and imported to different environments.