11Siebel Test Automation Execution
Siebel Test Automation Execution
This chapter includes information about the Siebel test automation execution process. It includes the following topics:
Setting Up the Jenkins Server
The Siebel Test Execution process is performed on the Jenkins server using the custom plugin designed for this process.
To install the Jenkins Server
Navigate to Jenkins webpage.
In the LTS release section, select the drop down next to the war name, then select Windows.
The Jenkins zip file will be downloaded.
Extract the Jenkins.msi file from the zip file.
Double click the .msi file to launch the Jenkins installer and follow the instructions to complete the installation.
Click Finish.
Jenkins will be launched in your default browser.
After completing the installation, copy the Administrator password from the path.
c:\Users\intbuild\.jenkins\secrets\initialAdminPassword
Click Skip Plugin Installations.
Enter the field name and values as shown in the table below:
Click Save and Finish.
The Jenkins setup is ready.
Click Start to use Jenkins.
The following welcome message is displayed - “Welcome to Jenkins!” Your Jenkins server is up and running.
Once the Jenkins setup is done, the Jenkins application will be launched by default on port 8080. However, if some other application is already running on this port, then you must change the port number in the jenkins.xml file.
For example, if the installed location of Jenkins is : C:\Program Files (x86)\Jenkins\ then change the port number to 8090 (it could be any port number) in the xml file and restart the Jenkins server.
You can start or stop the Jenkins server is using the Windows service running by name 'Jenkins'
Setting Up and Configuring the Siebel Test Execution Plugin
The Jenkins custom plug-in allows the user to interact with Siebel Master Server. Follow the procedure below to setup and configure the Siebel Test Execution plugin.
Prerequisites:
Before installing the Siebel Test Execution (STE) plugin, you must set up the proxy server configuration. The STE.hpi plugin is available in the following location SIEBEL_SERVER_ROOT/plugins
You must install the Node and Label Parameter Plugin from Manage Jenkins -> Manage Plugins -> Available tab.
To set up the proxy server configuration
Navigate to Manage Jenkins -> Manage Plugins, then select Advanced tab and add the following proxy server settings.
Note: You can check with your IT administrator for the proxy settings.HTTP Proxy Configuration Server
www.<your company proxy server>.com
Port Number
<NN>
To install the custom plugin
From the Upload Plugin pane, navigate to the plugin location, select the STE plugin and click Upload.
The status of the STE plugin installation is displayed in the screen.
Click Installed to check if the STE plugin has been installed successfully.
Setting up the Jenkins Slaves
Before setting up the Jenkins slaves, you must configure the Master server.
To configure the Master server
In the Jenkins home page, click Manage Jenkins-> Manage Nodes.
Click Master Node, then click Configure. Enter the following details:
Field Name Value Labels
Master
Usage
It is recommended to use this node to the maximum extent.
Navigate to Jenkins -> Manage Jenkins -> Configure Global Security
Check the Enable Security option in the Configure Global Security window and set the TCP Port for JNLP Agents as Random.
To append the Slave machines
Navigate to Manage Jenkins -> Manage Nodes -> New Node from the Jenkins home page.
Enter the Node name [machine_name.domainname.com] and check the Permanent Agent option.
Click OK and enter the value for the fields as shown in the following table.
Field Name Value Name
machine_name.domainname.com
Description
NA
Remote Root Directory
C:\jenkins-slave
Labels
STEDemo
Usage
It is recommended to utilize this node to the maximum extent.
Launch Method
Launch the slave agents via Java Web Start
Availability
Keep this slave online.
Click Save.
Copy the Slave.jarfile to any folder in the client machine.
From the destination folder, run the following command in the command promptslave from the command line.
java -jar slave.jar -jnlpUrl
http://machinename_domainname:NN/computer/machinename_domainname/slave-agent.jnlp-secret <hexadecimal key for the node>
Configuring the Siebel Test Execution Job
You can configure the Siebel Test Execution job from the Configuration Screen.
To create a job to be executed on single machine, you must select the Freestyle project and create one job.
You can configure the Siebel Test Execution job from the Configuration Screen.
Select the check box "Restrict where this project can be run and provide the label expression similar to the one that was defined while configuring the slave machine, e.g. STEDemo"
To configure the STE Job
Navigate to Build -> Add build Setup.
Note: The Siebel Test Execution option will be automatically displayed if the custom plugin provided by Siebel is already installed.Select the Siebel Test Executor from the drop down.
The Build Test Execution screen is displayed with the fields listed in the table below.
Field Name Value DISA Location
c:\DISA
Siebel Server URL
http://xyzmlb.domainname.com/1660/Siebel/
User Id
SADMIN
Password
........
When you install the STE custom plugin, the command field value is populated by default ((java -jar %DISA_DIR%\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\KWDPresetup.jar)
Click the help text shown against each field in the right hand corner. Enter the details for all the fields.
Configuring Multiple Jobs
To execute a job on multiple nodes (client machines), you must create two Jenkins jobs - one with the Freestyle Project and the other one with the MultiJob Project.
To create a MultiJob project, you must install the MultiJob plugin which is available by default in the Jenkins repository. The Siebel Test Execution job will be executed from the Siebel Test Executor Job.
You can define ‘Master’ in the label expression to restrict the job to run on the Master with same configurations specified above.
In a MultiJob you need to add the build step named as ‘MultiJob Phase’.
Update the settings:
Phase Name : <Provide any phase name>
Phase Job : <Name of the Siebel Test Execution Job created above>
Advanced Button :
Kill the phase on : <Select Never option>
Uncheck all the selected check box options.
From ‘Add Parameters’ Drop Down -> Select NodeLabel Parameter and Predefined parameters options.
Provide the Name and Node same as label name defined for the slave machines.
In Predefined Parameters set the value as DISA_DIR=C:\\DISA
Job Execution Type : Running phase jobs in parallel.
Continuation condition to next phase : Always
Executing the Siebel Test Jobs
You can execute a single job or run mutilple jobs simultaneously. To execute a single job, with a (Siebel RUn-ID), you must select the STE Job Freestyle project. To execute mutilple jobs with (Siebel-RUN-IDs’), you must select the the STEJobExecutor Multijob Project. This will internally execute the STEJOB on various nodes including the (client machines) simultaneously.
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 recorded scripts to the test sets and creating a MasterSuite with the test scripts.
To execute the batch run automation
Click New.
The Test Run # field value is auto populated and the default value for the Status field will be displayed as "Hold".
Select the Master Suite using the Master Suite Id field and select the Application Version.
Save the Record.
Select the Client Operating system. For example, Windows, Android or iOS.
Save the record.
Check if the values for the Server Credentials and User List are populated.
Select the Client Operating System as Windows (if it is a normal desktop run).
Enter the Client IP address if you have chosen the operating system as iOS.
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.
Before running the scripts on a Mobile platform, ensure that the plink.exe and psexec.exe files are available in the "..\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\exe" location.
After running the scripts, the results will be displayed in the Firefox browser. The recommended version for the FireFox browser is 31.4esr.
Update the Application Type, OS and URL in the Server Credentials applet.
Update the password in the User List applet.
Review the record.
Click Schedule Run.
After you click the Scheduled Run button, the record status will be changed to "Requested" and the following files must 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 automation execution configuration records are updated with the appropriate status and the resultant xml files are added as attachments.
The following table provides you with the list of the scripts available in the sample database.
Master Suite | Test Set | Sequence | Test Scripts | Description |
---|---|---|---|---|
COM_SampleDBDemo _Desktop |
COM_Sample DB_ABOFlows |
1 |
COM_SampleDB_ NewOrderFlow |
Ron Weasley is a residential customer looking for a good deal on a new family wireless plan. Ron calls the wireless carrier for a quotation. The contact center agent looks up Ron Weasley's account, browses the product catalog, selects the best family wireless package and offers three new phones for Ron's family at varying price points. |
2 |
COM_SampleDB_ UpdateOrder |
David Smith is an existing residential customer who has a family wireless plan. David calls the wireless carrier to add additional lines to his family package. Contact Center agent looks up David Smith's account and adds 5 new lines to David's account. The CRM system notifies the agent that David's current package is limited to 4 lines. The agent adds 3 new lines as one line is already associated to David, selects the options for text messages, data plan and reviews the order details with David. |
||
3 |
COM_SampleDB_ DebundlePromotion |
David is an existing residential customer who has a family wireless plan. David calls the wireless carrier to remove his spouse from the family package and make it an individual plan. |
||
4 |
COM_SampleDB_ Upgrade PromotionFlow |
Suzie Harera is a residential customer who has a basic quad play bundle - Internet, TV, Home Phone and Wireless Phone. Suzie calls the contact center to upgrade to a premium quad play bundle. |
||
COM_SampleDB_ BulkOrder |
1 |
COM_SampleDB_ BulkOrder_New OrderFlow |
Axiom Financial Group is a business customer that purchases 50 wireless service plans with pre-assigned numbers from the Communication Service Provider's Account Manager. The Account Manager connects to the CSP's commerce application, creates an account list, and places a bulk order to onboard 50 new users. Alternatively, Axiom Financial Group requests an optional feature "WLAN Subscription" to be added for 20 of its loyal users. Competitive pressure requires the communication service provider to upgrade all Promo 60 plan customers to Promo 120 plan. |
|
2 |
COM_SampleDB_ BulkOrder_Modify Flow |
|||
3 |
COM_SampleDB_ BulkOrder_Upgrade OrderFlow |
|||
COM_SampleDB_ ProductOffer |
1 |
COM_SampleDB_ ProductOffer_Data Setup |
Communication Service Provider creates a targeted mass market offer across varying channels (Web, Retail store, SMS). Customer accepts the offer(s) using a single click: offer to add free worldwide calls to their current wireless package at a 50% discount during the holiday season, upgrade their SMS package to higher package or auto-renew their contract. |
|
2 |
COM_SampleDB_ ProductOffer_ ModifyAdd |
|||
3 |
COM_SampleDB_ ProductOffer_ ModifyReplace |
|||
4 |
COM_SampleDB_ ProductOffer_ ModifyUpgrade |
|||
COM_SampleDB_ PG_Flows |
1 |
COM_SampleDB_ PG_Data_Setup_1 |
Product administrator verifies the community offer (promotion group) defined in the system using Siebel administrator (SADMIN)login. PG Scenario 3 is disconnects a Silver Participant membership and Nation 550 Minutes bundle promotion for PGA2 child account and it also disconnects the entire promotion group from PGA1 account. |
|
COM_SampleDB_ PG_Data_Setup_2 |
||||
2 |
COM_SampleDB_ PG_Scenario_1 |
|||
3 |
COM_SampleDB_ PG_Scenario_2 |
|||
5 |
COM_SampleDB_ PG_Scenario_3 |
|||
COM_SampleDB Demo_Telco |
COM_SampleDB_ Telco_Desktop |
1 |
COM_SampleDB_ Telco_DataSetup Flow |
CitiExpress is a business customer. Tim is a B2B sales rep for a leading Communication Service Provider (CSP). CitiExpress is Tim's customer with a wireless contract for 1000 employees. CitiExpress wants to change the barring options for 4 of their employees' phones and change the SIM number for an employee who had recently lost his phone. Tim connects to CSP's commerce application, searches for his customer, and place an order to change the barring options and change the SIM card number. |
COM_SampleDB_ Telco_Mobile |
1 |
COM_SampleDB_ Telco_ChangeSIM _Messages |
||
2 |
COM_SampleDB_ Telco_SelectAll _Remove |
|||
3 |
COM_SampleDB_ Telco_ChangeSIM_ SubmitOrder |
|||
4 |
COM_SampleDB_ Telco_AddRemove_ Flow1 |
|||
5 |
COM_SampleDB_ Telco_AddRemove_ Flow2 |
|||
6 |
COM_SampleDB_ Telco_DataCleanUp |
|||
COM_SampleDBDemo _Mobile |
COM_SampleDB _PartnerCommerce |
1 |
COM_SampleDB_ PartnerCommerce_ NewOrder |
Samuel Crenshaw is a partner user and places an order on the wireless carrier's partner portal. Samuel uses his iPad to login to the partner portal, browses the partner catalog, compares product attributes and prices, adds the best product to his cart, selects and configures options and places an order on behalf of his customer. |
2 |
COM_SampleDB_ PartnerCommerce_ Compare |
|||
COM_SampleDB_ eSales |
1 |
COM_SampleDB_ eSales_ERIGBY Login |
Kate Allison is shopping for a high speed Internet, TV and long distance phone service for her home. Kate uses her iPad to navigate to the communication service provider's web store, browses the product catalog and adds the standard triple play package to her shopping cart. Kate completes the new user registration form, reviews the shipping and pricing details and submits an order. Eleanor Rigby is a business user and logs in to the communication service provider's web store to track the orders placed on behalf of her company. Additionally, Eleanor registers and administers other users of her company. |
|
2 |
COM_SampleDB_ eSales_Flow1 |
|||
Demo Flow for Service Request |
Service Request Test Set |
1 |
Workflow Activation |
Eric Hess is an existing customer, who calls up to the customer care to raise a service request, that could be a problem related to products or services purchased from the company. Tim Malone the call center agent receives the call and creates an SR for the issue raised by the customer. Tim enters the required details to the SR including description, asset details, contact details, etc. |
2 |
Create SR |
|||
3 |
Associate Product |
|||
4 |
Update SR |
|||
5 |
Check Entitlements |
Tim checks customer's entitlements for the service. Once done, he looks for the possible solution for the issue raised by the customer and adds the solution to the SR. He decides that a field engineer needs to visit the customer site, so he creates an activity and assign it to an appropriate field engineer to fix the problem. |
||
6 |
Associate Asset |
|||
7 |
Associate Entitlements |
|||
8 |
Associate Solution |
|||
9 |
Add Activity Plan |
|||
10 |
Delete Data |
Delete all the newly created data from the environment. |
Sl # | Script Name / Action to be Performed | Test Step # | Current Data | Proposed Change |
---|---|---|---|---|
1 |
Script - COM_SampleDB_ Telco_ChangeSIM_ SubmitOrder
|
|
|
|
34 |
Row Number is NULL |
Row Number > Active_Record |
||
2 |
Script - COM_SampleDB_ Telco_DataSetupFlow |
|
|
|
Action ->Update |
1 |
Component Alias > Siebel Power Communications |
Component Alias >Siebel Power Communications_Setup |
|
Action ->Insert @ Test Step #26 |
27 |
|
Click on New and enter the below values. Keyword ->HierarchicalList Applet RN - > Order Entry - Line Item List Applet (Sales) Row # -> 2 Action -> Expand Variable ->NULL Save the record
Note: Select Renumber from the Menu.
|
|
Action ->Insert @ Test Step #108 |
109 |
|
Click on New and enter the below values. Keyword ->HierarchicalList Applet RN - > Order Entry - Line Item List Applet (Sales) Row # -> 2 Action -> Expand Variable ->NULL Save the record
Note: Select Renumber from the Menu.
|
|
Action ->Insert @ Test Step #133 |
134 |
|
Click on New and enter the below values Keyword ->HierarchicalList Applet RN - > Order Entry - Line Item List Applet (Sales) Row # -> 2 Action -> Expand Variable ->NULL Save the record
Note: Select Renumber from the Menu.
|
|
3 |
Script - COM_SampleDB_ Telco_ChangeSIM_ Messages |
|||
Action ->Update |
1 |
User Name > ANTHYAGA |
User Name > SADMIN |
|
Action ->Update |
22 |
ExpectedMessage Substring> Unable to complete SIM Swap. There is a stolen or admin bar for the selected service. Remove the stolen or admin bar to continue with your request.(SBL-ORD-51426) |
ExpectedMessageSubstring > "Unable to complete SIM Swap. There is a stolen or admin bar for the selected service. Remove the stolen or admin bar to continue with your request."(SBL-ORD-51426) |
|
4 |
Script - COM_SampleDB_ Telco_SelectAll_Remove |
|
|
|
Action ->Update |
12 |
Item RN >Select All|Select All |
Item RN > SelectAll|Select All |
|
Action ->Update |
13 |
End Action >OK |
End Action > NULL |
|
Action ->Update |
14 |
Item RN >Select All|Select All |
Item RN > SelectAll |
|
Action ->Update |
22 |
Item RN >Select All|Select All |
Item RN > SelectAll |
|
Action ->Update |
24 |
Item RN >Select All|Select All |
Item RN > SelectAll |
|
5 |
Script - COM_SampleDB_ Telco_ChangeSIM _SubmitOrder |
|
||
Action ->Update |
34 |
Row Number is NULL |
Row Number > Active_Record |
|
6 |
Script - COM_SampleDB_ Telco_AddRemove_ Flow2 |
|
|
|
Action ->Update |
4 |
Value>TelcoExpress_ 05252017_22343988 |
Value>@TelcoAccName |
|
Action ->Update |
6 |
Value>TelcoExpress_ 05252017_22343988 |
Value>@TelcoAccName |
|
Action ->Update |
9 |
ItemRN> Select All |
ItemRN > SelectAll |
|
Action ->Update |
11 |
ItemRN> Select All |
ItemRN > SelectAll |
|
Action ->Update |
13 |
ItemRN> Action |
ItemRN> Product Name |
|
Action ->Insert @ Test Step #8 |
9 |
|
Click on New and enter the below values. Keyword ->ClickButton Applet RN- >TOUI AssignBar Buttons ItemRN -> Cancel Request End Action -> NULL Save the record
Note: Select Renumber from the Menu.
|
|
Action ->Insert @ Test Step #9 |
10 |
|
Click on New and enter the below values. Keyword - > ClickLink Applet RN -> TOUI CustDash Action Launchpad ItemRN ->Expand Applet Value/Variable -> NULL Save the record
Note: Select Renumber from the Menu.
|
|
Action ->Insert @ Test Step #10 |
11 |
|
Click on New and enter the below values Keyword -> ClickButton Applet RN -> TOUI CustDash Action Launchpad Item RN -> AddRemoveBar EndAction -> NULL Save the record
Note: Select Renumber from the Menu.
|
|
Action ->Insert @ Test Step # 21 |
22 |
|
Click on New and enter the below values Keyword -> SortColumn Applet RN -> TOUI AssignBar Order Items Item RN -> Service Id Sorting Order -> Asc Save the record.
Note: Select Renumber from the Menu.
|
|
7 |
Script - COM_SampleDB _Partner Commerce_Compare Action ->Update |
|
|
|
6 |
ItemRN>Select All |
ItemRN> SelectAll |
||
8 |
Script - COM_SampleDB _eSales_Flow1 |
|
|
|
Action ->Update |
1 |
User Name> GUESTCST |
User Name> PortalApplication |
|
Action ->Update |
15 |
Row Number > 3 Value/Variable>NULL |
Row Number > remove value in this field. Value/Variable>IPTV Service |
|
Action ->Update |
38 |
ItemRN> Select All|Select All |
ItemRN> SelectAll |
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 following Toolsconfig keywords, update the following fields:
Siebel Tools Machine (For example, slc10xyz)
Siebel Tools Path (For example, C:\Siebel\23066\Tools)
Siebel Tools Machine Username (For example, USERONE)
Siebel Tools Machine Password (For example, Any valid password).
Perl Path (For example, c:\\perl\\bil\\perl.exe)
Database: DSN name|USERNAME|PASSWORD
If the Master Suite contains Inboundwebservicecall keyword, update the following fields:
EAI: (For example, slc10xyz:16661|USERONE|pwd)
Syntax: machinename:EAI portnumber|username|password -> values are separated by pipe
If the Master Suite contains the ServerConfig keyword, you must update the following fields in the Server Credentials applet.
EAI Server Port (For example, 16661)
Server Home Path (For example, c:\23066)
Server Login Credentials (For example, abc10xyz:xyxyx|USERONE|PASSWORD)
Note: xyxyx is a sample representation for the port number.Syntax: machinename:portnumber|username|passwrod -> values are separated by pipe.
- Gateway Machine and TLS Port (For example, xab10xyz:xyyx)
Creating Test Results
After the batch run is completed for a Master suite, the results will be updated as an Attachment in the Release Screen -> Automation Execution Configurations view as an Attachment for each Test Run Id.
The Attachment name will begin with the Test Run number (#) mentioned in the parent list applet. Once this file is available, you can click the Create Test Passes button to create Test Results in Siebel. After the Results are successfully created, the following message will be displayed "Test Pass Created Successfully. You can Query in Test Pass View Starting with <Test Run #>"
Viewing Test Results
After the Test pass is created successfully , you can navigate to the Release Screen > Test Pass View. Query for Test Run # to get the results. This will show you the number of test cases passed/failed/aborted/not executed.