1. Testing Business Applications Guide
  2. Configuring Multiple Batch Runs

Configuring Multiple Batch Runs

Siebel test automation supports parallel execution where you can execute one batch run at the same time as multiple other batch runs on the same (DISA) client. Each batch run runs as a parallel but isolated browser session on the same client, without impacting other sessions running in parallel. The parallel execution of multiple automation batch runs maximizes the utilization of compute resources and minimizes the overall cycle time.

To run multiple batch runs in parallel on a given client on the same or different browsers, complete the steps in the following procedure.

To configure multiple batches to run in parallel

  1. Execute and schedule your batch runs as required – for more information, see Executing the Automation Batch Run. Make sure that the latest STE.hpi is installed on Jenkins and verify that it has a "Parameters" field.

  2. Configure the -–parallel=nn parameter on the Jenkins Siebel Test Execution, where –- is a double hyphen and nn is the maximum number of batches to run on the client. This parameter is provided by the Siebel Test Execution plugin on Jenkins, in the "Parameters" field.

    • For example, –-parallel=nn will initiate a query for test execution records, limiting the number to 3.

    • If 4 or more test execution records are available, only 3 batch runs will be initiated in parallel.

    • By default (if -–parallel=nn is not specified), one test execution record will be queried.

  3. After the –-parallel=nn parameter is configured, the following describes how multiple parallel batch runs work on a virtual machine:

    1. When the keyword framework is initiated on a virtual machine, it starts the number of threads as specified by the –-parallel=nn parameter.

      • For 8 GB RAM, 2 to 3 parallel suites are recommended.

      • For 16 GB RAM, 3 to 5 parallel suites are recommended.

    2. Each thread is assigned a test execution record, identified by Run Id (the Row Id of the test execution record), and a browser session starts that is independent of any other browser session.

    3. Each test execution record or Master Suite runs from start to finish according to the sequence of specified test scripts, and results are collated into a report that is stored in a folder named by the "Run Id" of the test execution record under SiebelTestAutomation\TestExecutions.

    4. The following subfolders are created under the Run Id folder, along with any relevant files:

      • Reports

      • Resources

      • Scripts

    5. After a master suite run completes, the reports are zipped up and uploaded to the Siebel Test Execution record as an attachment.

    6. New runs cannot be initiated until all the threads in a parallel batch run are complete.