1. Testing Business Applications Guide
  2. Executing the Automation Batch Run

Executing the Automation Batch Run

This topic describes the steps involved in executing the automation batch run. You can proceed with this task after adding the test scripts to the test sets and creating a Master Suite with the test scripts.

To execute the batch run

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

  2. Click New (or the plus (+) icon) on the Form applet.

    The Test Run # field value is auto populated and the default value for the Status field is Hold.

  3. Select the Master Suite using the Master Suite Id field and select the Application Version.

  4. Save the record.

  5. Check if the values for the Server Credentials and User List are populated.

  6. Select Windows as the Client Operating system (if this is a normal desktop run).

  7. Enter the Client IP address if you have chosen the operating system as iOS.

    1. If the Operating System (OS) is iOS, enter the value for the Client IP Address, MAC Machine Username, MAC Machine Password and Mobile Port fields.

    2. Before running the scripts on a Mobile platform, ensure that the plink.exe and psexec.exe files are available in the following location: "..\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\exe".

    3. After running the scripts, the results will be displayed in the Firefox browser. The recommended version of Firefox browser is the latest version for which a compatible Web driver is available.

  8. Update the Application Type, OS and URL in the Server Credentials applet.

  9. Update the password in the User List applet.

  10. Review the record.

  11. Click Schedule Run.

    After you click the Scheduled Run button, the record status will change to Requested and the following files will be available in the Attachments applet:

    • batchconfig.xml

    • MasterSuite.csv

    • Resources.zip (if the Resources.zip is available in the Master Suite Attachments applet).

    Once the scheduled run is completed, the Siebel Test Execution records are updated with the appropriate status and the resulting xml files are added as attachments.

Note: You can use the Master Suite and test scripts available in the sample database for a batch run. For more information about the scripts available in the sample database and the actions performed by the scripts in the sample database, see Sample Database Test Scripts.

You can now proceed with the task of updating the other fields.

  • Client Operating System: Windows (if it is a desktop run).

  • Client Operating System: iOS (if it a mobile iOS run).

  • Client Operating System: Android (if it is a mobile Android run).

  • If the Master Suite contains Invokeperl and Serverconfig as keywords, then the Perl Path is mandatory (for example: c:\\perl\\bil\\perl.exe).

  • If the Master Suite contains the Toolsconfig keyword, then update the following fields:

    Field Description Sample Value

    Siebel Tools Machine

    Machine Name

    slcxxxxxx.domain.com

    Siebel Tools Path

    Tools install folder path

    C:\Siebel\Tools

    Siebel Tools Machine Username

    Login id for machine

    Domain/User1 or just user name

    Siebel Tools Machine Password

    Password for machine

    <xyzabc>

    Siebel Tools DSN

    DSN name

    SiebelDSN

    Siebel Tools User

    Tools user id

    sadmin

    Siebel Tools Password

    Tools password

    <xyz>

  • If the Master Suite contains the Inboundwebservicecall keyword, then update the following fields:

    Field Description Sample Value

    EAI Machine Name

    Machine Name

    slcxxxxxx.domain.com

    EAI Port Number

    HTTPS Port Number

    16661

    EAI Server User

    EAI user name

    user123

    EAI Server Password

    Password for EAI user

    <abcxyz>

  • If the Master Suite contains the ServerConfig keyword, then you must update the following fields in the Server Credentials applet.

    Field Description Sample Value

    Server Home Path

    Siebel Server install folder path.

    C:\Siebel\

    Siebel Server Machine

    Siebel Server machine name.

    slcxxxxxx.domain.com

    Siebel Server User

    Server machine user name.

    user123

    Siebel Server Password

    Password for Server machine user.

    <abcxyz>

    Siebel Gateway Machine

    Siebel Gateway machine name.

    slcxxxxxx.domain.com

    TLS Port

    TLS port number.

    443

    AI Server Port

    HTTPS port number

    16661
Note: If you receive the error message, HTTP Status 405: Method not allowed, this could be due to a required Business Service not having the required access permission in Siebel. To resolve this issue, navigate to the Administration Application screen, then the Business Service Access view, create a record selecting Automation Rest Service, provide the access permissions, and then restart the Siebel Server.

Parameters Applet:

  • Click New to add a record. Provide a Parameter Name and corresponding Value. Ensure to use exact name and case in your Test Scripts.

  • Once Schedule Run button is clicked, parameters are added to batchconfig.xml, and New, Delete buttons are disabled.

  • At the start of the batch run, before starting Test Script execution, Keyword framework, automatically creates variables for each of the parameter with same Name and initializes each with respective Value. These variables can be directly used in Test Scripts and/or Data Set Condition expressions.

  • Example: For a parameter with Name = ENV, Value = UAT in Parameters applet, a variable @ENV is created with value UAT

  • Example: For a parameter with Name = SSOUser, Value=UserXYZ, a variable @SSOUser is created with value UserXYZ.

  • Adding Parameters is also supported in REST API.

Add and Delete buttons in Server Credentials Applet:

  • If there are no records in Server Credentials (which means that Launch keyword has not been used), Keyword Framework will create a Chrome webdriver instance and the handle is made available for CustomExtension keyword. If a browser other than chrome is required, ensure to have a record in Server Credentials Applet reflecting the choice of browser. In either of the case, ensure appropriate browsers and corresponding drivers are available on the client machine.

  • You may add a record for EAI Server details for alias name used in InvokeREST keyword.

  • Ensure not to delete the records that are automatically added by application upon saving the Test Execution record.

Copying a Test Execution record

  • In the Test Execution View, select a Test Execution record. Click on Applet Menu → Copy Record (CTRL+B) menu item.

    This action copies the selected record, along with various values from the original record.

  • Following are the field values copied and new values set:

    Test Execution Form Applet:

    The fields Test Run #, Status, schedule, Test Harness Machine, and Runs Completed, are set to their default values.

    Rest of the field values are copied as-is over to new record.

    Server Credentials List Applet:

    All values are copied for latest Application Alias entries found on Test Scripts.

    Users List Applet:

    This applet is repopulated with unique user ids from Test Scripts.

    Parameters List Applet:

    Values from this applet are not copied, as these are not stored in database tables. The entries need to be created manually.

    Attachments List Applet:

    No attachments are copied.