1. Testing Business Applications Guide
  2. Configuring the Test Run

Configuring the Test Run

Configuring a test run involves creating a test execution record and running the test scripts.

This task is a step in the Process of Implementing Siebel Open UI Keyword Automation Testing.

Creating the Test Execution Record

  1. Navigate to Site Map, Release screen, then the Test Execution view.

  2. Click the plus (+) icon to create a new configuration record.

  3. Complete the fields with the values shown in the following table.

    Field Description Sample Value

    Master Suite id

    Master Suite

    Select a Master Suite record from the drop-down list.

    The Row id and the name of the selected Master Suite appear in the respective fields.

    Application Version

    The version number of the application.

    To create the application version records, navigate to Site Map, Quality screen, then the Release Product Administration view.
    Note: You can create records in this view, and the same would be available as Application Version values in the Test Execution view.

    1.2.0

    Notify

    Check this box to enable Notifications on Test Execution Status changes. For example, when Test Execution Status changes to Completed, following record will show on Notifications Summary.

    Test Run #: <Run id of Test Execution> ( <name of Master Suite> ) Test Execution Status: <Status value> mm/dd/yyyy

    Example: Test Run #: 88-ZFU21 ( MySuite01 ) Test Execution Status: Completed 07/17/2023

    Checked or Unchecked

    Run Reference

    Enter value of Label from Jenkins Node or group of Nodes. Ensure the value is an exact match with Node Labels, including case. Ensure there are no spaces in the Label text.

    Test Execution record will be redirected to run on a matching Node only.

    This field is optional - default is blank.

    Refer to section Configuring the Siebel Test Execution Job.
    Note: When Run Reference Field is used, ensure to provide Parameter --runReference=<Same label value as in Run Reference field> on Test Execution job (or build step) configuration.

    Client_Pool_A, myclientxyz

  4. In the Server Credentials applet, select the Application Type (such as Desktop_Chrome), the URL details, and the OS (Operating System) and Language.

  5. Click Schedule Run, and the status will be updated to Requested.

    Assuming that the Jenkins Server setup is ready, the status will be updated to Scheduled.

    The attachment files are created in the Attachments applet. For example: batchconfig.xml, mastersuite.csv, and Resources.zip.