Siebel Open UI Extension
The Tosca Siebel OpenUI Extension is part of the Tricentis Tosca setup.
Siebel Open UI Controls
Siebel Open UI applications can be steered with the Tosca XBrowser Engine. Modules are created by using Tosca XScan (see also chapter "Scan Modules").
You can steer the following standard controls as described in chapter "Steering Controls":
This chapter includes a detailed description of all Siebel Open UI specific controls.
Disabling extra checks if Siebel page is busy
You can disable the check if a Siebel page is busy by using the test configuration parameter SiebelBusyCheck or the steering parameter SiebelBusyCheck. If you add the parameter to your TestCase and set the value to False, the system will refrain from performing extra checks to see if the Siebel page is busy.
Date Picker (SiebDatePicker)
Siebel Date Picker controls contain a popup menu for entering the date, and they are steered implicitly via the input field of the control.
Date Picker with open popup window
Input
Values are inputted into a Date Picker control via the Value column.
Tosca however uses a textbox control if the input should be made via the popup window (see chapter "Popup Menu (Textbox)").
|
Syntax: |
MM/DD/YYYY [hh:mm <AM/PM>] Please note that the date format used depends on the system settings of your workstation. |
|
Example: Entering values into Date Picker controls |
Verify
The following properties can be verified via the Value column:
|
Property |
Value |
Description |
|
Enabled |
True/False |
Verifies whether the calendar can be steered |
|
IsRequired |
True/False |
Verifies whether the input is required via the calendar popup window |
|
Text |
<value> |
Verifies the text contained in the input field of the control |
|
|
This example verifies whether the date picker control Charter Award Date is enabled and editable.
Example: Entering values into date picker controls |
Menu (SiebMenu)
Siebel Menus are hierarchically structured menus.
Siebel Menu
Input
Menu entries are selected by specifying the menu entries, which have to be separated by the following string: ->.
|
Syntax: |
<MenuEntry1>-><MenuEntry2>->etc. |
|
|
The entry Site Map is selected from the menu View.
Example of selecting a menu entry |
You can use regular expressions for input actions. This requires that the value of the setting Accept unknown dynamic expressions is set to Yes.
|
|
View->{REGEX[^O.*Help]} In this example the engine searches for an entry in the View menu which starts with an O. The entry is additionally comprised of an arbitrary number of characters and contains the value Help. A possible solution would for instance be to select the entry Open IHelp here. |
Verify
Menu entries are verified via items of the Siebel Menu Control. These items must be manually created (see also chapter "Creating generic list items"). TreeNode must be specified as BusinessType. The value of the configuration param AlgorithmicAssociation must be set to ListItems.
Menu item names are verified via the Value column. The following properties can be verified in the Value column:
|
Property |
Value |
Description |
|
Exists |
True/False |
Verifies whether the entry exists in the menu |
|
Enabled |
True/False |
Verifies whether the entry can be selected (and steered) |
|
ResultCount |
<value> |
Verifies the number of menu entries |
|
|
TestStep 01 verifies whether the value xyt exists in the menu. TestStep 02 verifies whether the menu entry Navigate->First Record is available for selection. TestStep 03 verifies whether the menu View contains 10 entries. TestStep 04 verifies whether the menu entry View->Site Map contains an entry of the value test.
Examples illustrating how to verify menu entries |
Notification
Siebel Notification Controls contain a list of notifications which can be steered.
Siebel Notification Control
Input
The list containing the notifications must be opened in advance by clicking on the red button which indicates the number of available notifications (Notification Count).
Entries can be selected in the notification window.
Notifications are either selected via the title or an index using a leading number sign. For further information on control steering, please see also chapter "Control types".
|
Value |
Description |
|
{Click} |
The entry is selected. |
|
{Close} |
The entry is closed (This applies to Siebel Open UI Version 8.2.2.4). |
|
|
The example below illustrates how to close the first notification in the notification window.
Example: Performing inputs into a notification control |
Verify
Notification names are verified via the Value column. The following properties can be verified via the Value column:
|
Property |
Value |
Description |
|
Text |
<value> |
Verifies the notification text |
|
|
The example below verifies the text of the notification Application Summary.
Example: Verifying a notification |
Popup Menu (Textbox)
Some Siebel controls contain a popup menu at the right end of an input field which allows the corresponding values to be defined, for instance calculator controls.
Example of a popup menu in an input field
These popup menus can be openend by using the value {OpenPopup}.
|
|
The first TestStep in the example below opens a popup window (Calendar Control), and the input values are defined in the subsequent TestStep.
Example: Opening a popup window |
Slider
The Siebel Slider Control is part of the Siebel Calendar Control. This can be used for specifying the exact time. Hour and minute values are positioned accordingly using the corresponding sliders.
Siebel Slider Control
Input
Hours and minutes are specified in the Value column.
|
|
The slider controls are positioned as follows: 10 hours and 55 minutes.
Example: Inputs made into a Siebel Slider Control |
Verify
Hour and minute values are verified via the Value column.
Tab (SiebPageTabs)
SiebPageTabs controls contain tabs and views which can be steered within a tab.
Example showing a tab with views
Input
Inputs are made by specifying the required tab in the Value column.
Pages within tabs are selected via the following syntax:
|
Syntax: |
<TabName>-><View name> |
|
|
The Opportunities List view is selected from the Opportunities tab.
Example showing how to select a tab view |
You can use regular expressions for input actions. This requires that the value of the setting Accept unknown dynamic expressions is set to Yes.
|
|
{REGEX[^Opportu]}->Opportunities List In this example the engine searches for a tab which starts with Opportu, and it selects the menu entry Opportunities List in this tab. |
Verify
Tab control views are verified via control items. These items must be manually created (see also chapter "Creating generic list items"). TreeNode must be specified as BusinessType. The value of the configuration param AlgorithmicAssociation must be set to SubItems.
View names are verified via the Value column. The following properties can be verified via the Value column:
|
Property |
Value |
Description |
|
ResultCount |
<number> |
The system verifies either the number of SiebPageTabs controls, the tabs in a control or the views within a tab, depending on the selection. |
|
Count |
<number> |
The system verifies the number of all visible tabs. Any tabs within drop-down menus that are currently invisible are ignored in this context. |
|
ScreenCount |
<number> |
The number of tabs is verified. Any tabs within the drop-down menu that are currently invisible are included. |
|
ViewCount |
<number> |
The system verifies the number of views in a tab. |
|
ActiveScreen |
<value> |
The system verifies whether the specified tab is active. |
|
ActiveView |
<value> |
The system verifies whether the specified view of a tab is selected. |
|
|
Example illustrating how to verify properties |
Table
Siebel tables are steered as described in chapter "Steering Controls".
Siebel Table
Input
The Tosca Siebel OpenUI Engine supports the following click operations:
-
{CLICK}
-
{DOUBLECLICK}
Verify
The following properties can be verified via the Value column:
|
Property |
Value |
Description |
|
ClassName |
<value> |
The system verifies the internal class name of the control. |
|
Enabled |
True/False |
The system verifies whether the table is active/editable. |
|
attributes_ariaselected |
<number> |
Verifies the index of the currently selected row. Hidden rows are ignored. The index of the first row is set to 0. |
|
ColumnCount |
<number> |
This verifies the number of columns that are currently visible in the table. |
|
RowCount |
<number> |
Verifies the number of rows that are currently visible in the table. |
Toolbar
SiebelToolbars contain various buttons which can be steered.
SiebelToolbar
Input
Buttons are clicked by using the Toolbar Control and by specifying the button title in the Value column.
|
|
The Report(s) button is clicked here:
Example: Clicking on a toolbar button |
Verify
Toolbar buttons are verified via Toolbar Control items. These items must be manually created (ListItem) (see also chapter "Creating generic list items").
Button names are verified via the Value column. The following properties can be verified via the Value column:
|
Property |
Value |
Description |
|---|---|---|
|
Exists |
True/False |
Verifies whether the button exists in the toolbar |
|
Enabled |
True/False |
Verifies whether the button can be clicked in the toolbar |
|
ResultCount |
<number> |
Verifies the number of buttons in the toolbar |
|
|
Examples illustrating verify operations in a toolbar |
