Implementing Siebel Open UI Keyword Automation Testing

This chapter provides an overview of implementing Siebel Open UI keyword automaton testing in software development projects. It contains the following topics:

Overview of Siebel Open UI Keyword Automation Testing

Siebel Open UI keyword automation testing is based on the Keyword Driven Framework. The Keyword Driven Framework is an automation testing framework which uses action words for testing.

The four main parts to each keyword automation step are:

Action to perform (Keyword)
Object to act upon
Input data
Choice of closing action.

A test case or script is made up of a set of sequenced test steps as shown, for example, in the following table.

Table lists the sequence of steps involved in keyword automaton.

Action or Keyword	Target Object	Inputs	Choice of closing action
Click a button	Repository name of an applet and button.	Any required closing action, such as, clicking OK or Cancel, (after the button is clicked).	Click new
Input value	Repository name of applet and button.		Enter a value in the Name field.

Process of Implementing Siebel Open UI Keyword Automation Testing

This topic describes the tasks involved in implementing Siebel Open UI keyword automation testing using the following test scenario:

I want to automate a test script using keywords that will, for example, create a new product and add it to Quote.

Perform the following tasks to implement keyword automation testing for this scenario:

Creating a Test Script
Adding Test Steps to Test Scripts
Grouping Test Scripts into a Test Set
Grouping Test Sets into a Master Suite
Configuring the Test Run

Creating a Test Script

This task describes the procedure involved in creating a new test script.

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

To create a test script

Make sure that the Siebel application is running.
Navigate to the Sitemap, Release, then the Test Scripts view.
Click the plus (+) icon to create a new Test Script.

Enter values for the fields shown in the following table.

Column Name	Value	Description
Name	xyz	Name of the test script.
Test Script Description	Test	Description of the test script.
Status	Active	Status of the test script
Reference ID	xyz_abc	The reference id of the test script.
Team name	ABC	The name of the team.
Release	IP2017	The name of the specific release.
Test Environment	All, Demo etc	Specifies the test environment.

From the Test Scripts menu, choose Save Record.
A new test script is created.

Adding Test Steps to Test Scripts

This task describes the procedure involved in adding test steps to test scripts.

This task is a step in the Process of Implementing Siebel Open UI Keyword Automation Testing. Ensure that the Siebel application is up and running.

To add test steps to test scripts

Navigate to the Sitemap, Release, then the Test Scripts view.
Drilldown on the name of the test script to which you want to add test steps.
Click the plus (+) icon to create a new test step.

In the Test Step Form applet, enter field values for the fields shown in the following table. Note the following:

The first test step (or test sequence number 1) must be the Launch keyword.

After you select a Keyword, the fields are rendered dynamically as required for the keyword.

Table Fields and Sample Values for Test Step Form Applet

Field Name	Value	Description
Test Step Sequence	1	Sequence number for the test step.
Description	Login	Description of the Keyword
Keyword	Launch	Enter this keyword to log into the application.
Paste Attributes	Not Applicable	Not Applicable.
Component Alias	Can be any name	ID associated with the test script.
User Name	CCHECNG	Name of the user.
Clear Browser	Y	Enter this value to clear the browser cache.
Screenshot Required	Not Applicable	Select this option to capture the corresponding step performed in the test step.

Save the record.

Test Steps View

The Test Steps View is a new applet similar to Test Steps applet under Test Scripts.

This view exposes the Test steps at the first level. The records are in read-only mode and you cannot create any records here. You can only query and view the records.

The Test Steps View exposes the inputs and RNs given in the keyword as separate columns. Import/Export is supported for this applet.

In case the input for a keyword is changed, user can export records for that particular keyword, modify the input value and import it. Using the Test Sets view, you can also know how frequently each keyword is used i.e., by querying on the keyword, you can get the number of records for that keyword.

To edit the Test Steps, navigate to the Sitemap, Release, then the Test Steps.

Capturing Automation Attributes for Test Steps

This task shows you how to use the attributes pop-up window to capture automation attributes for test steps.

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

Before capturing automation attributes for test steps, the following prerequisites apply:

Ensure that the following behavior settings are set by navigating to Tools, User Preferences, Behavior.
Set Navigation Control to Tab.
Set Theme to Aurora.
Ensure that the Siebel application is running in AutoOn mode.
Ensure that the URL command is set to the AutoOn mode, for example, as follows:
http://machinenumber:domainname:portname/siebel/app/callcenter/enu?SWECmd=AutoOn
Being in the AutoOn mode helps you to capture the automation attributes when navigating through the application.

To capture automation attributes for test steps

Start the Siebel application in a new browser.
To capture the automation attribute for a specific object or control, do the following:
1. Position the mouse over the object or control for which the automation attributes are needed (for example, the plus (+) icon).
2. Press the CTRL key on your keyboard and right-click your mouse button simultaneously.
  The Siebel Automation Information dialog box appears.
3. Copy the string value from the COPY STRING field and paste it into the Paste Attributes field of the Test Step.
4. Tab out of the Paste Attributes field in the Test Step.
  The data will be automatically populated in the target object fields. For example: the AppletRN and ItemRN fields.

About Keyword Reference

The Keyword Reference.doc is available in the SiebelTestAutomation folders. The document lists all the keywords and provides you with information on how to use keywords with examples.

Note: The place holders for NULL values IPH1;IPH2;IPH3 are not available in the document.

Grouping Test Scripts into a Test Set

This task shows you how to group test scripts into a test set.

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

To group test scripts into a test set

Navigate to the Sitemap, Release, then the Test Set view.
Click the plus (+) icon to create a new Test Set.

Enter values for the fields shown in the following table.

Field	Description	Sample Value
Name	Name of the test set.	Xyz
Description	Description of the test set.	Test
Test Plan Name	Name of the test plan.	Test_xyz
Release	Name of the release.	1718
Team	Name of the team.	Tranformers
Status	Status of the test set.	Active
External ID	The external ID associated with the test set.	Testplan_1

Drill down on a value in the Name field and then click the plus (+) icon or the Add Test Scripts button to associate test scripts to the selected Test Set.
Update the Sequence field for each associated test script.

Grouping Test Sets into a Master Suite

This task shows you how to group test sets into a Master Suite.

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

To group test scripts into a Master Suite

Navigate to Sitemap, Release, then Master Suites.
Click the plus (+) icon to create a new test set.

Enter values for the fields shown in the following table.

Field	Description	Sample Value
Name	Name of the test set	xyz
Description	Description of the test set	Test
Status	Status of the test set	Active
Test Plan ID	ID associated with the test set	Test1_001
Team	Specifies the corresponding name of the team.	Titans, Transformers etc.
Release	Specifies the appropriate release version.	17.0

Drilldown on a value in the Name field, then click the plus (+) icon or the Add Test Sets button to associate test sets to the selected Master Suite.
If the mastersuite contains the following keywords, you must add the required files in the respective folders.
- Folder Name: Resources
- Keywords:
  - Inboundwebservicecall
  - Invokeperl
  - Serverconfig
  - fileupload

After including the files, you can zip the folder (that is, Resources.zip) and attach the Resources.zip file in the MasterSuite Attachments Applet.

Configuring the Test Run

This task shows you how to create an execution configuration record and then run the test scripts:

Creating the Execution Configuration Record
Running the Test Scripts

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

Creating the Execution Configuration Record

This task shows you how to create an Execution Configuration record.

From the Site Map, navigate to Release, then the Automation Execution Configuration screen.
Navigate to Release Product Administration view, Create New Record
Click the plus (+) icon to create a new configuration record.
A new record is created.

Enter the value for the following fields:

Field	Description	Sample Value
Master Suite id	Name of the Master Suite id	xyz-770
Application Version	The version number of the application. To create the application records, navigate to Site Map, Quality, Release Product Administration view. Note: You can create records in this view, and the same would be available as Application Version values in the Automation Execution Configuration.	1.2.0

In the Server Credentials applet, select the Application Type (such as, Desktop_Chrome), the URL details, and the OS (Operating System) and Language.
Click Schedule Run. The status will be updated to Requested.
Assuming that the Jenkins setup is ready, the status will be updated to Scheduled.
The attachment files are created in the Attachments applet. For example, the batchconfig.xml file, mastersuite.csv file and Resources.zip file.

Enabling Oracle Business Intelligence Publisher for Test Automation

To enable Oracle Business Intelligence Publisher (BIP) for Test Automation, you must enter the BIP specific parameters. As a prerequisite, ensure that BIP is integrated with Siebel prior to test execution.

The format for entering the parameters in the Batch mode and Unit mode are given below.

Batch Mode

Enter the following details in the Test Execution screen.

For example, http://slcxxxxxx:9502/xmlpserver/services/publicreportservice_v11|slcxxxxxx:9500|slcxxxxxx:9502|SADMIN|ldap

Note: The parameter specified above is separated by pipe delimiters.

The first part of the parameter specifies the outbound webservice, the second one specifies the BIP console and port, the third one specifies the BIP XMLP server name and port followed by the user credentials i.e., user name and password.

Unit Mode

Update the following parameters in the unitconfig.xml file.

<BIP-OUTBOUNDWEBSERVICE>http://slcxxxxxx:9502/xmlpserver/services/publicreportservice_v11</BIP-OUTBOUNDWEBSERVICE>
<BIP-SERVERNAME>slcxxxxx:9500</BIP-SERVERNAME>
<BIP-SERVERXMLP>slcxxxxx:9502</BIP-SERVERXMLP>
<BIP-USERNAME>SADMIN</BIP-USERNAME>
<BIP-PASSWORD>ldap</BIP-PASSWORD>

Note: The BIPserver.jar file is packaged in DISA and available in C:\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\lib folder.

After installing DISA, the bip.pl will be availabe in the following location:

<DISA Install location>\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\perl

To perform BIP Automated script execution, you need to move the bip.pl to the folder <DISA Install location>\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Resources\invokeperl

Using BIP Automation, you can verify all Interactive, Scheduled and Parameter based report generation.

Siebel Test Automation Folder

The Siebel Test Automation folder structure contains the required folders for executing the csv script. The Framework folder contains all the required JARS and library files. The following folder structure is available when you install DISA.

Table Automation folder structure.

Folders / FilesType		Type	Execution
Framework	Exe	Do not modify	Contains necessary Exe files which are used in the SiebelTestAutomation Framework
	Lib		Contains necessary Library files (Jar files) which are used in the SiebelTestAutomation Framework
	Perl		Contains necessary Perl scripts which are used in SiebelTestAutomation Framework
	SiebelTestAutomation.jar		Compiled executable Jar which drives KWD execution
Reports		Post- execution	The folder gets created post execution, generates execution results for review.
Resources	fileupload	Script authoring	Folder containing user developed files needed for fileupload, inboundwebservicecall, invokeperl, toolsconfig, serverconfig keywords.
	inboundwebservicecall		Folder containing user developed files needed for inboundwebservicecall.
	invokeperl		Folder containing user developed files needed for invokeperl.
	toolsconfig		Folder containing user developed files needed for toolsconfig.
	serverconfig		Folder containing user developed files needed for serverconfig.
Scripts	Samplescript.csv		Place holder for csv scripts.
batchconfig.xml		Pre-setup	XML File which has the configuration details of execution(URL,username password, script location). The batchconfig.xml file will be copied by the Jenkins scheduler if it is a STE run. The unitconfig.xml will be use for UPT run.
User_opted_operation.txt			A text file which contains the information like Pause, Resume and abort.User has the option to Pause/Resume/Abort the current execution by updating the value in User_opted_operation text.
Log_randomnumber.log			A text file which contains the information like Pause, Resume and abort.User has the option to Pause/Resume/Abort the current execution by updating the value in User_opted_operation text.