Header

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

SFDC Actions enable you to perform automation testing on a Salesforce application using Classic, Lightning , and Aura themes.

General SFDC Actions

SFDC general actions denote those actions for which objects are not needed for execution.

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

SFDC.ClickButton

This action clicks the specified button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

buttonName

Enter the button name you want to click.

Yes

String

Example:

SFDC.ClickButton "Edit"

SFDC.ClickEditIcon

This action clicks the edit/pencil icon button. The labelName parameter for this action is the Title attribute value excluding the Edit word.

Example:

SFDC.ClickEditIcon "List"

SFDC.ClickTab

This action clicks the specified tab.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

tabName

Enter the tab name you want to click.

Yes

String

Example:

ClickTab       "Accounts Check"

SFDC.CreateNewEntity

This action clicks the New button to create new entity/record such as Leads, Contacts, Opportunity, and so on.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

tabName

Enter the tab name you want to click based on the label name.

Yes

String

Example:

CreateNewEntity       "Accounts Check"

SFDC.Logout

This action allows you to log out from the SFDC application.

This action does not contain any parameters.

Example:

SFDC.Logout

SFDC.ScrollEntireTable

This action scrolls the table.

Example:

SFDC.ScrollEntireTable

Note: If you apply this action on a infinitely-loading table, then action will also perform infinite loading. As a result, the execution will get into a infinite loop.

SFDC.SelectTabs

This action selects a specified tab.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

tabName

Enter the tab names you want to select.

Yes

String

Example:

SelectTabs       "Accounts Check"

SFDC.SortColumnData

This action sorts the column data.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

columnName

Enter the column name you want to sort.

Yes

String

sortOrder

Specify the sorting order, i.e., Ascending or Descending.

Yes

String

Example:

SFDC.SortColumnData "CloseDate"

SFDC.SwitchView

This action switches to a specified view.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

viewName

Enter the respective SFDC view to which you want to switch. The values are lightning and classic.

Yes

String

Example:

SFDC.SwitchView "Classic"

SFDC.SwitchUser

This action switches to a specified user.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

userName

Enter the username of the user to which you want to switch.

Yes

String

Example:

SFDC.SwitchUser "John"

SFDC.SwitchToTab

This action switches to a user-specified tab.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

tabName

Enter the tab name to which you want to switch.

Yes

String

Example:

SwitchToTab       "Accounts Check"

SFDC.SwitchApp

This action switches to a user-specified app.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

appName

Enter the app name to which you want to switch.

Yes

String

Example:

SwitchApp       "Sales"

SFDC.WaitForLabel

This action waits for the label to be visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

labelName

Enter a unique object name for which you want to check the visibility.

Yes

String

maxTimeOutInSeconds

Enter the maximum timeout in seconds up to which you want the script to wait for a label to be visible.

Yes

String

Example:

SFDC.WaitForLabel "Username"

SFDCButton

On this Page:

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCButton class actions work for the following SFDC components:

  • button

  • button-group

  • button-icon

  • button-icon-stateful

  • button-stateful

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

StoreState

This action stores the state of the associated object. It supports the stateful objects only.
For example, when you click the Follow button, it changes to Following. Hence, the Follow button has two states: Follow and Following.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the object state.
No

String

Example:

StoreState        "Key 1"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter values, such as the actual value of the property

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue      "class"    "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible
  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"




SFDCCheckBox

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCCheckBox class actions work for the following SFDC components:

  • inputCheckbox
  • checkbox-group

The following table describes how Qualitia Automation Studio (QAS) identifies and adds a checkbox into the object repository when using the Qualitia Automation Recorder or Chrome Object Spy:


QAS Recorder and Chrome Object SpyExample

If the checkbox is not part of a group: 

(inputCheckbox)

Adds the checkbox name as an object in the format: <ObjectName>_inputCheckbox. 

The QAS recorder also adds the associated action that was captured.

If a checkbox name is called Occupation, then it adds the object as Occupation_inputCheckbox.

If the checkbox is part of a group:

(checkbox-group)


Adds the checkbox group as an object in the format: <CheckboxGroupName>_checkboxGroup. 

The QAS recorder also adds the associated action that was captured. If the associated action contains any parameter, then QAS Recorder adds the selected checkbox name in the associated parameter.

If a checkbox group is called Industry and you select the checkbox called ITthen an object called Industry_checkboxGroup is added and the selected checkbox is added in the associated parameters.

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

Check

This action checks the checkbox.

This action is not applicable for the checkboxGroup component.

Example:

Check

CheckByValues

This action checks the checkboxes as per the values that you specify.
 

This action is not applicable for the inputCheckBox component.

Parameter Name

Parameter Description

Mandatory

Data Type

values

Enter the values of the checkboxes that you want to select by separating them with a tilde (~) and a delimiter (^).

Yes

String

Example:

For example, if a checkbox group called Stage contains multiple checkboxes: Open, Closed, Closed Won.  You can check them.

CheckByValues      "Open~^Closed~^Closed Won"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

StorePropertyValue

This action stores the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue       "key"       "class"

Uncheck

This action deselects the checkbox of a page.

This action is not applicable for the checkboxGroup component.

Example:

Uncheck 

UncheckByValues

This action deselects the checkboxes as per the values that you specify.

This action is not applicable for the inputCheckBox component.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

values

Enter the name of the checkboxes that you want to deselect by separating them with a tilde (~) and a delimiter (^).

Yes

 String

Example:

For example, if a checkbox group called Stage contains multiple checkboxes: Open, Closed, Closed Won.  You can uncheck them.

CheckByValues      "Open~^Closed~^Closed Won"

VerifyChecked

This action verifies whether the checkboxes are selected as per the values that you specify.

If the SFDC component is inputCheckBox, then specify a single value.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the values of the checkboxes that you want to select by separating them with a tilde (~) and a delimiter (^).

No

String

Example:
For example, in the Classic theme, the New Accounts Checks page contains the set[num123] checkbox. You can verify if it is checked.

VerifyChecked         "set[num123"

For example, if a checkbox group called Stage contains multiple checkboxes: Open, Closed, Closed Won. You can verify if they are checked.

VerifyChecked      "Open~^Closed~^Closed Won"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue      "class"    "fr small"

VerifyUncheck

This action verifies whether the checkboxes are deselected as per the values that you specify.

If the SFDC component is inputCheckBox, then specify a single value.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the values that you want to deselect by separating them with a a tilde (~) and a delimiter (^).

Yes

String

Example:

For example, in the Classic theme, the New Accounts Checks page contains the set[num123] checkbox. You can verify if it is unchecked.

VerifyUncheck         "set[num123"

For example, if a checkbox group called Stage contains multiple checkboxes: Open, Closed, Closed Won. You can verify if they are unchecked.

VerifyUncheck      "Open~^Closed~^Closed Won"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility          "True"

SFDCDateTime

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCDateTime class actions work for the SFDC component InputDateTime.

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

Clear

This action clears the text present in the specified text box.

This action does not have any parameters.

Example:
Clear

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver


Set

This action sets the specified date and time values on the associated datetime field.

While recording in the Lightning theme, QAS Recorder adds the specified date value in the dateValue parameter and adds the default time value in the timeValue parameter. If you also record the editing of the default time, the recorder adds a new step with the Set action that contains the selected date and the modified time.


Parameter Name

Parameter Description

Mandatory

Data Type

dateValue

Enter the date you want to set on the date field. 

Note: If the object already has a default value, the action clears the value.

No

String

timeValue

Enter the time you want to set on the time field. 

Note: If the object already has a default value, the action clears the value.

NoString


Example:

Set       "06/16/2021"   "12:30 PM"

StorePropertyValue

This action stores the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.  You can store the property value of date or time, or both of them.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

fieldNameEnter dateProperty or timeProperty that you want to store on the associated datetime field, or enter both if you want to store both.YesString

key

Enter the key name to store the property name.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue   "both"    "key"       "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as Class, Id, name, and role, and parameter value, such as the actual value of the property. You can verify the property value of date, time, or both.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

fieldName

Enter either dateProperty or timeProperty that you want to verify on the associated datetime field, or enter both if you want to verify both.

YesString

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue     "both"    "class"   "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyVisibility    "True"

SFDCDualListbox

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCDualListbox class actions work for the SFDC component Dual-listbox.

Add

This action moves the selected options from the first list to the second list.

Parameter Name

Parameter Description

Mandatory

Data Type

elements

Add the values that you want to move to the second list by separating them with a delimiter (^).

Yes

Array


Example:

Add      "Campaign 1^Campaign 2^Campaign 3" 

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

Remove

This action removes the selected items from the second list that you specify.

Parameter Name

Parameter Description

Mandatory

Data Type

elements

Enter the values that you want to remove from the second list by separating them with a delimiter (^).

Yes

String


Example:

Remove   "Campaign 4^Campaign 11"

RemoveAll

This action removes all the selected options from the second list.

Example:

Remove All

StoreAvailableItems

This action stores all the items present in the first list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store all the items present in the first list.

Yes

 String

Example:

StoreAvailableItems      "key"                     

StoreSelectedItems

This action stores all the items present in the second list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store all the items present in the second list.

Yes

 String

Example:

StoreSelectedItems     "key"     

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"   "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute as specified in the DOM structure.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue      "class"    "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyVisibility            "True"

SFDCEdit

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCEdit class actions work for the following SFDC components:

  • input
  • inputCurrency
  • inputEmail
  • inputNumber
  • inputPhone
  • inputRichText
  • inputText
  • inputTextArea
  • inputURL
  • inputSecret

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

Clear

This action clears the text present in the specified text box.

This action does not have any parameters.

Example:
Clear

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver


Set

This action sets the value on the associated object.


Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value you want to set on the associated object. 

Note: If the object already has a default value, the action clears the value.

Yes

String


Example:

Set       "India"

SecureSet

This action encrypts the value you enter. It helps to hide the value for security purposes, such as the password that is used to log in to the application.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

text

Enter the text you want to enter in the specified object.
Format: Encrypt(TEXT TO BE ADDED)

Yes

String

Example:

SecureSet    "Encrypt(Abc)"    "vHpmlfI4R3PQkCN4sZnuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

In this case, QAS encrypts the data ABC to a secured text, such as shown above. The text is encrypted immediately when you move the focus from the Text parameter in the Test Case Editor screen after entering ABC as the Text parameter value. 

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property name.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue       "key"       "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue      "class"         "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyVisibility    "True"

SFDCLink

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCLink class actions work for the following SFDC components:

  • navigation

  • route-link

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue     "key"    "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue       "class"         "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility    "True"

SFDCLookUp

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCLookUp class actions work for the Lookup component.


CreateNewEntity

This action creates a new entity in the lookup.
This action does not have any parameters.

Example:

CreateNewEntity

ClearEntry

This action clears the options selected in the lookup.

This action does not have any parameters.

Example:
ClearEntry

MouseOver

This action hovers over the specified object.
This action does not have any parameters. 

Example:

MouseOver


SearchAndSelect

This action finds the value that you specify using the Search feature in the lookup screen, and then selects the value.

Parameter Name

Parameter Description

Mandatory

Data Type

recordName

Enter the value that you want to search in the Search box to select the value.

Yes

String


Example:

SearchAndSelect       "John Smith"

StorePropertyValue

This action stores the property of the specified object using property names, such as class, id, name, and role, and   parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue     "key"       "class"

StoreSelectedItem

This action stores the selected item.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the selected item.

Yes

 String

Example:

StoreSelectedItem     "key"     

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute  as specified in the DOM structure.

Yes

String

valueEnter the property value that you want to verify.YesString

Example:

VerifyPropertyValue     "class"     "fr small"

VerifySelectedItem

This action verifies if the specified item is selected.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value that you want to verify whether it is selected.

Yes

String

Example:

VerifySelectedItem     "John Smith"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility    "True"

SFDCMultiselectPickList

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCMultiselectPickList class actions work for the SFDC component html multiselect and checkboxMenuItem.

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

DeselectItemsByIndex

This action deselects the selected items by the index numbers that you specify.


Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the index numbers of the items that you want to deselect by separating them with a delimiter (^).

Yes

Array


Example:

For example, a multi-select picklist called as Select Multi Stages contains the values, such as Open, Closed, Closed Won, Prospecting, Qualification, Needs Analysis, and Any. If you do not want Closed and Closed Won, then enter their index numbers as 2^3.

DeselectItemsByIndex     "2^3"


DeselectItemsByText

This action deselects the selected items by texts that you specify.


Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the items that you want to deselect by separating them with a delimiter (^).

Yes

Array


Example:

For example, a multi-select picklist called as Select Multi Stages contains the values, such as Open, Closed, Closed Won, Prospecting, Qualification, Needs Analysis, and Any

DeselectItemsByText     "Closed^Closed Won^Needs Analysis"

SelectItemsByIndex

This action selects items by index numbers that you specify.


Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the index numbers of the items that you want to select by separating them with delimiter (^).

No

Array


Example:
For example, a multi-select picklist called as Select Multi Stage contains the values, such as Open, Closed, Closed Won, Prospecting, Qualification, Needs Analysis, and Any. If you want to select Closed and Closed Won, then enter as "2^3".

SelectItemsByIndex     "2^3"

SelectItemsByText

This action selects items by texts that you specify.


Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the items that you want to  select by separating them with a delimiter (^).

Yes

Array


Example:
For example, a multi-select picklist called as Select Multi Stage contains the values, such as Open, Closed, Closed Won, Prospecting, Qualification, Needs Analysis, and Any

SelectItemsByText     "Closed^Closed Won"

StoreAllItems

This action stores all the items present in the associated multi-select picklist.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store all the items available in the picklist.

Yes

 String

Example:

StoreAlltems        "key"                     

StoreItemCount

This action stores the number of items present in the associated multi-select picklist.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store all the items in the multi-select picklist.

Yes

 String

Example:

StoreItemCount     "key"              

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"       "class"

StoreSelectedItems

This action stores all the selected items.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store all the selected items.

Yes

 String

Example:

StoreSelectedItems       "key"     

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyItemsPresent

This action verifies the presence of the specified items.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfvalues

Enter the values that you want to verify in the list.

Yes

Array

Example:
For example, a multi-select picklist called as Select Multi Stage contains the values, such as Open, Closed, Closed Won, Prospecting, Qualification, Needs Analysis, and Any

VerifyItemsPresent      "Open^Closed^Closed Won"

VerifyPropertyValue

This action verifies the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute in the DOM structure

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue      "class"      "fr small"

VerifySelectedItems

This action verifies if the items are selected in the multi-select picklist as per the values that you specify.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the values that you want to verify.

No

Array

Example:
For example, a multi-select picklist called as Select Multi Stage contains the values, such as Open, Closed, Closed Won, Prospecting, Qualification, Needs Analysis, and Any

VerifySelectedItems      "Open^Closed^Closed Won"

VerifyUnselectedItems

This action verifies if the items are not selected in the multi-select picklist as per the values that you specify.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the values that you want to verify.

Yes

Array

Example:

VerifyUnselected    "Needs Analysis^Prospecting"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyVisibility                          "True"

SFDCPickList

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCPicklist class actions work for the following SFDC components: 

  • select
  • combobox
  • radioMenuItem
  • input-select
  • input-select-option

The following table describes how Qualitia Automation Studio (QAS) identifies and adds a pick list into the object repository when using the Qualitia Automation Recorder or Chrome Object Spy:

SFDC ComponentAdded by Qualitia Automation Recorder or Chrome Object Spy
select

<picklistname>_select

combobox<picklistname>_combobox
radioMenuItem<picklistname>_radioMenuItem
input-select<picklistname>_inputSelect

input-select-option

<picklistname>_inputSelect

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

SelectItemByText

This action selects the item that you specify.


Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the item that you want to select

Yes

String


Example:

In Classic theme, the Opportunities page contains the field: Stage, which has 11 options, such as Open, Closed, Closed Won, and Prospecting.

SelectItemByText    "Prospecting"

SelectItemByIndex

This action selects the items for a pick    list as per the index number that you specify.


Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the index numbers of the item that you want to select.

No

String


Example:

In Classic theme, the Opportunities page contains the field: Stage in which Needs Analysis is the third option.

SelectItemByIndex     "3"

StoreAllItems

This action stores all the items present in the associated pick list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store all the items present in the pick list.

Yes

 String

Example:

StoreAlltems          "key"             

StoreItemsCount

This action stores the number of items present in the associated pick list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store number of items in the pick list.

Yes

 String

Example:
In Classic theme, the Opportunities page contains the field: Stage, which has 11 options. You can store the number of options (11) into a variable.

StoreItemsCount           "key"               

StoreSelectedItems

This action stores the selected items present in the associated pick list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store the selected items present in the associated pick list.

Yes

 String

Example:

StoreSelectedItems            "key"     

StorePropertyValue

This action stores the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue     "key"       "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, by default the value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyItemsPresent

This action verifies the presence for the items that you specify. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the values that you want to verify in the list by separating them with a delimiter (^).

Yes

Array

Example:
In Classic theme, the Opportunities page contains the field: Stage, which contains 11 options, such as Value Proposition, Needs Analysis, Prospecting, and Qualification.

VerifyItemsPresent      "Value Proposition^Needs Analysis^Prospecting^Qualification"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute in the DOM structure

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue     "class"     "fr small"

VerifySelectedItems

This action verifies if the specified item is selected in the pick list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the value that you want to verify if it is selected in the pick list.

Yes

Array

Example:

VerifySelectedItems      "Prospecting"

VerifyUnselectedItems

This action verifies if the specified items are not selected in the pick list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

listOfValues

Enter the values that you want to verify that they are deselected in the pick list by separating them with a delimiter (^).

Yes

Array

Example:

VerifyUnselectedItems      "Needs Analysis^Prospecting^Qualification"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, by default the value is set to True during the test case execution.

No

String

Example:

VerifyVisibility    "True"

SFDCRichText

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCRichText class actions work for the SFDC component Input-rich-text.

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

Clear

This action clears the text present in the specified text box.

This action does not have any parameters.

Example:
Clear

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver


Set

This action enters the value on the associated RichText.


Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value you want to set on the RichText. 

Yes

String


Example:

Set     "John Smith works for Salesforce"

StorePropertyValue

This action stores the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue     "key"       "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action stores the property of the specified object using property names , such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name whose value needs to be stored under the specified key.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue     "class"     "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility  "True"

SFDCRadioButton

Note:

SFDC objects do not support the following features:

  • Polling Interval and Time Out on object level

  • Wait actions

All the SFDCRadioButton class actions work for the following SFDC components:

  • inputRadio
  • radio-group

The following table describes how Qualitia Automation Studio (QAS) identifies and adds a radio button into the object repository when using the Qualitia Automation Recorder or Chrome Object Spy:


QAS Recorder and Chrome Object SpyExample

If the radio button is not part of any radio group

(InputRadio)

Adds the radio button in the format:<ObjectName>_inputRadio. .

If the radio button name is Occupation, then the object is added as Occupation_inputRadio

If the radio button is part of any radio group

(RadioGroup)

Adds the radio group as an object in the format <RadioButtonGroupName>_radioGroup. The QAS Recorder also adds the selected radio button as the parameter as per the associated action.

If the radio button group name is Currencies and you select a radio button: US Dollars, then the group is added as Currencies_radioGroup and US Dollars as the parameter.

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

SelectByValue

This action selects the specified radio button as per its value. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value of the radio button that you want to select. 

Yes

String

Example:
SelectByValue     "Occupation"

SelectByIndex

This action selects the specified radio button as per its index number. The index number starts from 1. 

Note: For the inputRadio component, entering the index number other than 1 fails the execution.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

index

Enter the index number of the radio button.

No

String

Example:

SelectByIndex           "1"

StorePropertyValue

This action stores the property of the specified object using property names,such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"       "class"

VerifyEnability

This action verifies the enability of the specified object. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.
  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution
No

String

Example:

VerifyExistence      "True"

VerifyPropertyValue

This action stores the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name whose value needs to be stored under the specified key.

Yes

String

valueEnter the property value you want to verify.YesString

Example:

VerifyPropertyValue      "class"     "fr small"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible.
  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility          "True"

SFDCProgressBar

ProgressBar

The ProgresBar SFDC component supports the following actions:

  • StoreProgressPercentage

  • VerifyPropertyValue

  • StorePropertyValue

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

  • StoreExistence

  • MouseOver

  • Click

StoreProgressPercentage

This action stores the progress percentage of the progress bar component.

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the progress percentage.

Yes

 String

Example:

StoreProgressPercentage      "key_2"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String


Example:

VerifyVisibility     "True"

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                               "Key"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

SFDCProgressIndicator

ProgressIndicator

  • StoreStageState

  • VerifyStageHasError

  • VerifyIsStageCompleted

  • StoreCountOfCompleteStages

  • StoreStageNameByIndex

  • ClickStageByValue

  • ClickStageByIndex

  • Click

  • StorePropertyValue

  • VerifyPropertyValue

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

  • StoreExistence

  • MouseOver

StoreStageState

This action stores the state (Completed, Error, InProgress, Incomplete) of the progress indicator stage in the key provided.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the stage value.

Yes

 String

StageName

Enter the stage or attribute name whose value you want to store.

Yes

 String

Example:

StoreStageState      "key_3" “Completed”

VerifyStageHasError

This action verifies whether the provided stage has any error.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

StageName

Enter one of the following:

  • True to verify that the stage has an error.

  • False to verify that the stage has no error.
    Note: If you do not enter any value, the default value is set to True during the test case execution

Yes

 String

Example:

VerifyStageHasError      "Closed"

VerifyIsStageCompleted

This action verifies whether the provided stage is completed or not.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

StageName

Enter one of the following:

  • True to verify that the stage is completed.

  • False to verify that the stage is not completed.
    Note: If you do not enter any value, the default value is set to True during the test case execution

Yes

 String

Example:

VerifyIsStageCompleted      "Completed"

StoreCountOfCompleteStages

This action stores the count of completed stages in the provided key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the count of completed stages.

Yes

 String

Example:

StoreCountOfCompleteStages      "key_1"

StoreStageNameByIndex

This action stores the stage name in the key of stage who's Index is provided.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key in which the stage name will be stored.

Yes

 String

index

Enter the index of the stage.

Yes

String

Example:

StoreStageNameByIndex      "key_2" “2”

ClickStageByValue

This action clicks the stage of progress indicator component by value.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

stageName

Enter the stage name that must be clicked.

Yes

 String

Example:

ClickStageByValue      "Processing"

ClickStageByIndex

This action performs the click operation on the stage who's index is provided.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

index

Enter the stage index that must be clicked.

Yes

 String

Example:

ClickStageByIndex      "1"

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                               "Key"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

SFDCMessage

Message

The Message SFDC component supports the following actions:

  • Close

  • Click

  • MouseOver

  • StoreExistence

  • StoreHeader

  • StoreText

  • VerifyText

  • VerifyPropertyValue

  • StorePropertyValue

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

Close

This action closes the message when user clicks on cross button from message toast.

This action does not have any parameters.

Example:

Close

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                               "Key"

StoreHeader

This action stores the header value of message object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

messageKey

Enter the key in which header value of message toast will be stored.

Yes

String

Example:

StoreHeader                               "Success"

StoreText

This action stores the text of message.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key in which header value of message toast will be stored.

Yes

String

Example:

StoreText                               "S_T_key"

VerifyText

This action verifies the message text.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

message

Enter the expected text of message toast.

Yes

String

Example:

VerifyText      "Accounts Check “Qualitia" was created”

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"

SFDCSpinner

Spinner

The Spinner SFDC component supports the following actions:

  • Click

  • StoreExistence

  • VerifyPropertyValue

  • StorePropertyValue

  • MouseOver

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

  • WaitForProcessToComplete

  • WaitForInvisibility

  • WaitForVisibility"

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                 "Key"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"

WaitForProcessToComplete

This action waits for the process to be complete for spinner.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeForObjectTobeVisible

Enter the time (in seconds) to wait for the object to be visible.

No

String

timeForObjectTobeInvisible

Enter the time (in seconds) to wait for the object to be invisible.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the invisibility before exhausting timeout. 

No

String

keyStatus

Enter the key name under which the status of this step will be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to show in the report in case the expected condition is not satisfied. value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForInvisibility     "10"        "10"      “5” "keyStatus"       "Fail"

WaitForInvisibility

This action waits for the object to invisible. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to go invisible.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the invisibility before exhausting timeout. 

No

String

keyInvisibility

Enter the key name under which the status of this step will be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to show in the report in case the expected condition is not satisfied. value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForInvisibility     "10"          "5"     "keyInvisibility"       "Fail"

WaitForVisibility

This action waits for the object to be visible. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout. 

No

String

keyVisibility

Enter the key name under which the status of this step will be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to show in the report in case the expected condition is not satisfied. value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForVisibility     "10"          "5"     "keyVisibility"       "Fail"

SFDCErrorPanel

InputDefaultError

The InputDefaultError SFDC component supports the following actions:

  • VerifyMessage

  • Click

  • VerifyPropertyValue

  • StorePropertyValue

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

  • StoreExistence

  • MouseOver

VerifyMessage

This action verifies the message present in panel.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

VerifyMessage

Enter the message for which errorpanel message has to be verified.

Yes

String

Example:

VerifyMessage      "Complete this field"

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                               "Key"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

SFDCMultiLookUp

MultiLookUp

The MultiLookUp SFDC component supports the following actions:

  • ClearAll

  • SearchAndSelect

  • ClearEntries

  • MouseOver

  • StoreSelectedItems

  • VerifySelectedItems

  • VerifyPropertyValue

  • StorePropertyValue

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

  • StoreExistence

ClearAll

This action clears all the records from the Multilookup.

This action does not have any parameters.

Example:

ClearAll

SearchAndSelect

This action will search and select the provided record(s) from MultiLookup.

Parameter Name

Parameter Description

Mandatory

Data Type

recordNames

This parameter lists the name of records with separated delimeter.

Yes

String

Example:

SearchAndSelect       "Ab^Cd^Xy"

ClearEntries

This action clears the already selected entry/entries from multiLookup.

Parameter Name

Parameter Description

Mandatory

Data Type

recordNames

Lists the name of records with separated delimeter.

Yes

String

Example:

ClearEntries       "Ab^Cd"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

StoreSelectedItems

This action stores all the selected records from the Multilookup.

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which the selected record's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreSelectedItems       "key_1"

VerifySelectedItems

This action verifies all the selected records from the Multilookup.

Parameter Name

Parameter Description

Mandatory

Data Type

recordName

List of recordname with separated delimeter.

Yes

String

Example:

VerifySelectedItems       "Ab^Cd^Xy"

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility      "True"

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                "Key"

SFDCMenu

The SFDCMenu component supports the following actions:

  • SelectItemByIndex

  • SelectItemByText

  • VerifyPropertyValue

  • StorePropertyValue

  • MouseOver

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

  • StoreExistence

All the SFDCMenu class actions work for the following SFDC components: 

  • buttonMenuItem

  • actionMenuItem

The following table describes how Qualitia Automation Studio (QAS) identifies and adds a menu into the object repository when using the Qualitia Automation Recorder or Chrome Object Spy:

SFDC Component

Added by Qualitia Automation Recorder or Chrome Object Spy

buttonMenuItem

<componentname>_buttonMenuItem

actionMenuItem

<componentname>_actionMenuItem

SelectItemByIndex

This action selects items from SFDC Menu by using the index.

Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the menu item whose index is provided as an input.

Yes

String

Example:

SelectItemByIndex      "2" 

SelectItemByText

This action selects the items from the Menu by using the text.

Parameter Name

Parameter Description

Mandatory

Data Type

itemName

Enter the name of the item to be selected from menu items.

Yes

String

Example:

SelectItemByText      "Open" 

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                               "Key"

ActionMenuItem

The ActionMenuItem SFDC component supports the StoreExistence action.

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence                               "Key"

SFDCDataTable

DataTable

The DataTable SFDC component supports the following actions:

  • Click

  • ClickCellWithCellText

  • ScrollAndStoreRowCount

  • SortColumnData

  • StoreCellText

  • StoreExistence

  • StoreRowNumberOfCellText

  • StoreRowNumberOfMultipleCellText

  • VerifyCellText

  • VerifyRowData

  • WaitForCellChildElement

  • WaitForCellClickability

  • WaitForCellNonClickability

  • WaitForCellExistence

  • WaitForCellInnerTextContains

  • WaitForCellInnerTextNotContains

  • WaitForCellInnerTextMatchesPattern

  • WaitForCellInnerTextToBe

  • WaitForCellInnerTextNotToBe

  • WaitForCellVisibilty

  • WaitForCellInvisibilty

  • WaitForCellNonExistence

  • WaitForCellSelection

  • WaitForCellSelectStateToBe

  • WaitForCellStaleness

  • StoreRowNumberOfCellText

  • VerifyPropertyValue

  • StorePropertyValue

  • MouseOver

  • VerifyExistence

  • VerifyEnability

  • VerifyVisibility

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

ClickCellWithCellText

This action clicks on cell according to the provided cell data, rowNumber and columnNumber.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

cellText

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

Example:

ClickCellWithCellText “Test1” “5” “1”

ScrollAndStoreRowCount

This action scrolls till the last row and stores the total row count of the table.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key in which the row count will be stored.

Yes

String

Example:

ScrollAndStoreRowCount “key_1”

SortColumnData

This action sorts the data when the user clicks on heading cell of any particular column.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

columnName

Enter the name of the column.

Yes

String

sortOrder

Enter the direction in which the data needs to be sorted. 1 indicates ascending order and 2 indicates descending order.

No

String

Example:

SortColumnData “Account Name” “1”

StoreCellText

This action stores the cell data in key of the provided row number and column number.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

key

Enter the key in which the row count will be stored.

Yes

String

Example:

StoreCellText “1” “3” “key_2”

StoreExistence

This action stores existence of the object under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the existence's Boolean value will be stored. 

  • Stores True if the object exists.

  • Stores False if the object does not exist.

Yes

String

Example:

StoreExistence               "Key"

StoreRowNumberOfCellText

This action stores row number of the provided cell text.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

text

Enter the text of the cell.

Yes

String

columnNumber

Enter the index of the column.

No

Number

key

This will return the row number.

Yes

String

Example:

StoreRowNumberOfCellText             "Test1" “1” “key_3”

StoreRowNumberOfMultipleCellText

This action stores the row number with provided cell texts and column numbers, and the value is stored in the key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

text

Enter the text of multiple cells separated by delimiter.

Yes

Array

columnNumber

Enter the index of the column respective to cell data (separated by delimiter).

Yes

Number

key

This will return the row number.

Yes

String

Example:

StoreRowNumberOfMultipleCellText         "Test1^India^998660^Active" “1^2^3^4” “key_4”

VerifyCellText

This action verifies if the provided cell text value along with row number and column number is present in DataTable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

data

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

Example:

VerifyCellText         “Test1” "5" “1”

VerifyRowData

This action verifies if the provided cell text values along with row number is present in DataTable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

rowNumber

Enter a number which points to the row as per listOfValues.

Yes

Number

listOfValues

Enter the values with a separator/delimiter as caret.

Yes

Array

Example:

VerifyRowData         “2” "Test1^India^998660^Active"

WaitForCellChildElement

This action waits for the cell to contain child element until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of cell’s child element.

Yes

String

childLocatorValue

Enter the locator value of cell’s child element.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

key

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellChildElement “Xpath” “//*[@id=”brandBand_1]” “5” “2” “1”

WaitForCellClickability

This action waits until the cell of datatable becomes clickable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyClickability

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellClickability         “10” “2” “2” “5” "keyClickability" “Fail”

WaitForCellNonClickability

This action waits until the cell of datatable becomes non-clickable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyNonClickability

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellNonClickability         “10” “2” “5” “5” "keyNonClickability" “Fail”

WaitForCellExistence

This action waits for the cell to exist, i.e. it is in DOM, in datatable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

key

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellExistence         “10” “5” “5” “5” “keyNonClickability” “Fail”

WaitForCellNonExistence

This action waits for the cell to not exist, i.e. it is not in DOM, in datatable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

key

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellNonExistence         “10” “5” “2” “5” “key” “Fail”

WaitForCellInnerTextContains

This action waits for inner text of the cell to contain the expected text until timeout expires. If cell/datatable is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyInnerText

Enter the key in which the innerText needs to be stored.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellInnerTextContains         “Test1” “2” “5” “10” “5” “key” “Fail”

WaitForCellInnerTextNotContains

This action waits for inner text of the cell to not contain the expected text until timeout expires. If cell is found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyInnerText

Enter the key in which the innerText needs to be stored.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellInnerTextNotContains         “Test” “2” “5” “10” “5” “keyInnerText” “Fail”

WaitForCellInnerTextMatchesPattern

This action waits for inner text of the cell to match the specified pattern until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyInnerText

Enter the key in which the innerText needs to be stored.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellInnerTextMatchesPattern         “^t.*es$t” “2” “5” “10” “5” “keyInnerText” “Fail”

WaitForCellInnerTextToBe

This action waits for inner text of the cell to be the expected inner text until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyInnerText

Enter the key in which the innerText needs to be stored.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellInnerTextToBe         “TestUpdate1” “2” “5” “10” “5” “keyInnerText” “Fail”

WaitForCellInnerTextNotToBe

This action waits for inner text of the cell to not be the expected inner text until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text of the cell.

Yes

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyInnerTextNotToBe

Enter the key in which the innerText needs to be stored.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellInnerTextNotToBe         “TestUpdate1” “2” “5” “10” “5” “keyInnerText” “Fail”

WaitForCellVisibilty

This action waits for the cell to be visible in datatable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyvisibility

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellVisibilty         “10” “2” “3” “5” “keyVisibility” “Fail”

WaitForCellInvisibilty

This action waits for the cell to be invisible in datatable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keyInvisibility

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellInvisibilty         “10” “2” “5” “5” “keyInvisibility” “Fail”

WaitForCellSelection

This action waits for selection of the cell until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

key

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellSelection         “10” “5” “2” “5” “key” “Fail”

WaitForCellSelectStateToBe

This action waits for selection state of the cell to be expected state until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedSelectionState

Enter true for selected and false for deselected. The default value is true.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

keySelectionState

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellSelectStateToBe         “True” “10” “5” “3” “5” “key” “Fail”

WaitForCellStaleness

This action waits for staleness of the cell until timeout expires. If object is not found in the DOM, step status will fail. If key is provided, status will be stored in key. The status depends on the statusIfConditionNotSatisfied parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object visibility.

No

String

rowNumber

Enter the index of the row.

Yes

String

columnNumber

Enter the index of the column.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the object visibility before exhausting timeout.

No

String

key

Enter the key name under which the status of the step needs to be stored. It stores 0 for Pass, 1 for Fail, and 2 for Defect.

No

String

statusIfConditionNotSatisfied

Enter the status of the step you want to display in the report if the expected condition is not satisfied. The value for this parameter can be Pass, Fail, and Defect.

No

String

Example:

WaitForCellStaleness       “10” “5” “2” “5” “key” “Fail”

VerifyPropertyValue

This action verifies the property of the specified object using property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Enter the property or attribute name as specified in the DOM structure.

Yes

String

value

Enter the property value you want to verify.

Yes

String

Example:

VerifyPropertyValue      "class"    "fr small"

StorePropertyValue

This action stores the property of the specified object using  property names, such as class, id, name, and role, and parameter value, such as the actual value of the property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter a variable to store the property value.

Yes

 String

propertyName

Enter the property or attribute name whose value you want to store.

Yes

 String

Example:

StorePropertyValue      "key"    "class"

MouseOver

This action hovers over the specified object.

This action does not have any parameters. 

Example:

MouseOver

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution

No

String

Example:

VerifyExistence      "True"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

  • True to verify that the object is enabled.

  • False to verify that the object is disabled.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyEnability      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

  • True to verify that the object is visible

  • False to verify that the object is not visible.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

No

String

Example:

VerifyVisibility     "True"

  • No labels