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 8

This section contains detailed documentation for the following object classes of Web.

General Web Actions

Clipboard.Copy

This action copies the data given into the parameter to clipboard.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Text

Enter the text to add to the clipboard memory.

Yes

String

 Example:

Clipboard.Copy            "Qualitia Software Pvt. Ltd."

Clipboard.Clear

This action clears the data present on the clipboard memory.

This action does not have any input parameters.

Example:

Clipboard.Clear

CloseCurrentWindow

This action will close current window.  

This action does not have any parameter.

Example:
 CloseCurrentWindow

CheckExcelProcess

This action will check if the excel process is running.

This action does not have any parameter.

Description: It will pass if the excel process is running on your system. Otherwise, it will fail.

Example:

CheckExcelProcess

ConcatString

This action will concatenate the two strings and stores result string into a variable. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

str1

First string for concatenation

No

String

str2

Second string for concatenation

No

String

Key

Key name under which the result of concatenation will be stored. 

No

String

Example:

ConcatString  “Hello “ “World” “Result”

ComparetwoStrings (Deprecated)

This action will compare two string values. As it is deprecated, Qualitia recommends to use CompareString.

 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Str1

First string for comparison

No

String

Str2

Second string for comparison 

No

String

Example:

ComparetwoString  “hello“  “ hello”

ComparetwoInt

This action compares two integer numbers. Even a key can be passed as one of the parameters for comparison where the ComparetwoInt function will retrieve the value from the key and that value will be compared with another integer.

 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

int1

First integer value for comparison 

No

String

int2

Second integer value for comparison

 No

String

Example:

ComparetwoInt  “123“  “ 234”

DragAndDropToObject

This action drags the specified object and drops it in the position of another specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

dragLocator

Enter the locator value of an element to be dragged.

Yes

String

dragLocatorType

Enter the locator type of the element to be dragged.

Yes

String

dropToLocator

Enter the locator of an element whose location (i.e., whose centre-most pixel) will be the point where dragLocator is dropped.

Yes

String

dropToLocatorType

Enter the locator type of the element where the element will be dragged.

Yes

String

Example:
DragAndDropToObject                   "//div/img[@alt='abx']"            "xpath"           "abc"        "id"

OpenURL

This action opens the specified URL in the browser selected in the associated execution profile.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the URL that you want to open.

Yes

String

Example:

OpenUrl                               "http://www.google.com/ "

 

When using this action in Desktop projects, Qualitia defines its own set of system variables which can be used later when executing test cases. These variables are stored in Qualitia with their expressions (True or FALSE). Following is the list of system variables that Qualitia stores when executing the OpenURL action.

  • $$_ISIE: If browser type is set as IE (Internet Explorer), then this expression is stored as True. Here, other two ($$_ISFIREFOX and $$_ISCHROME) are stored as FALSE.

  • $$_ISFIREFOX: If browser type is set as FIREFOX (Mozilla Firefox), then this expression is stored as True. Here, other two ($$_ISIE and $$_ISCHROME) are stored as FALSE.

  • $$_ISCHROME: If browser type is set as CHROME (Google Chrome), then this expression is stored as True. Here, other two ($$_ISFIREFOX and $$_IE) are stored as FALSE.

Note: It is recommended to close all the unnecessary browsers before starting the test execution or object spying using UFT.

NavigateForward

This action navigates the browser to the next page.

This action does not have any parameter.

Example:

NavigateForward

NavigateBack

This action navigates the browser to the previous page.

This action does not have any parameter.

Example:

NavigateBack

RandomString

This action takes input as list of characters from user and gives random string as output of a specified length.

For example, if the string is "RTFTF" and length is "10", then it randomly generates a string as "RTFTTFRTFR".  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

CharacterList

The string given as input could be alphabetic, alphanumeric or numeric.

No

String

Length

The length of the random string to be generated.

No

String

strKey

The value of the random string is stored in strKey

No

String

Example:

RandomString  "32#$abd "            "12"      “abc”

ReplaceStringBySubString

This action replaces the specified part from the string with another string and stores the updated value into 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 in which you want to store the updated string.

Yes

String

inputString

Enter the string that you want to replace.

Yes

String

Find

Enter the part of the string that need to be replaced.

Yes

String

Replacewith

Enter the replacement text for the first string.

Yes

String

Start

Enter the start position. Default is 1. All characters before the start position will be removed.

No

String

count

Enter the number of substitutions to perform. Default is -1, which makes all possible substitutions.

No

String

Case Sensitive

Enter whether you want to consider case-sensitivity when comparing the string before replacement. Value for this parameter can be 0 or 1.

  • Set 0 for case-insensitive comparison.

  • Set 1 for case-sensitive comparison.

No

String

 

Example:

ReplaceStringBySubString          "Key"           "Australia"       "A"         "B"        "1"         "-1"        "1"

In this case,  the string Australia changes to Bustralia.

ReplaceAndStoreText

This action replaces a substring by another substring into a source string and stores the resulting string in the given key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

SourceText

The complete path of the file to be executed.

No

String

TextToBeReplaced

Substring that is to be replaced from the SourceText.

No

String

TextToBeReplacedBy

Substring by which replacement is to be done.

No

String

IsCaseSensitive

Indicates case sensitive.

Yes

String

Key

Key in which final output will be stored.

Yes

String

Example:

ReplaceAndStoreText              "India"          "i"               "Z"          "True"         "key1"

The result string will be IndZa.

ReplaceSubString

This action replaces a substring of an original string with a specified string.

For example, if a string is "WELCOMEWELCOME" and if you want to replace the second occurence of the substring "come" with gone". Then, the new string generated is 'WELCOMEWELGONE".

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

MainString

The original string.

Yes

String

SubString

The substring of the original string.

Yes

String

 

ReplaceString

The new string with which the substring is to be replaced.

Yes

String

 

Soccurrence

The number of times the substring occurs in the original string.

Yes

String

 

Key

 

The resultant value is stored in the Key.

 

Yes

String

iscasesenstive

Enter as True if you want to replace only when the case of letters of specified occurrence and substring matches.

Enter as False if you want to replace irrespective of whether the case of letters of the specified occurrence and substring matches.

Note: The default value is True.

Yes 

 String

Example

ReplaceSubString “welcome” “come”  “gone”  “1”  "True" “abc”

RandomNumber

This action takes lower and upper limit of a range as integer input and gives an output of a random integer number within that range.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

min

The string stores the lower limit of the range.

No

String

max

The string stores the upper limit of the range.

No

String

strKey

The value of the random number is stored in strKey.

No

String

Example

RandomNumber  "1"   "100"      

StorePageURL

This action stores the URL of the web page under the specified key. The stored value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store URL.

Yes

String

Example:

StorePageURL                   "Key"

RightClickTo(String X , String Y)

This action right-clicks at a definite location of the web page as specified by x and y coordinates. You cannot specify negative values to X and Y.

Parameter Name

Parameter Description

Mandatory

Data Type

String X

The X co-ordinate of the location

Yes

String

String Y

The Y co-ordinate of the location

       Yes

String

Example: 
String X = "100" , String Y = "100" . The right-click will occur at the location point (100,100).

ScrollTo(String X, String Y)

This action scrolls the Scrollbar of the web page to a definite location specified by x and y coordinates. You cannot specify negative values to X and Y.

Parameter Name

Parameter Description

Mandatory

Data Type

String X

The X co-ordinate of the location

Yes

String

String Y

The Y co-ordinate of the location

       Yes

String

Example:

String X = "100" , String Y = "100" . The scrollbar scrolls to the location point (100 ,100).

StoreFixNumber

This action stores the integer part of a specified number into the specified key. The stored key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name in which you want to store the updated string.

Yes

String

Number

Enter the number from which you want to store the integer part.

Yes

String

Example:

StoreFixNumber           "Key"              "6.4332"

In this case, the variable Key stores the value to 6.

StorePageTitle

This action stores the web page title under the specified key. The stored value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

E

r the key name to store page title.

Yes

String

Example:

StorePageTitle                   "Key"

StoreVariable

This action stores a particular string value under the specified key. This value can be used when developing test cases.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name to store variable.

Yes

String

data

Enter the value to be stored under the key name.

No

String

Example:

StoreVariable                   "url"                     "http://www.bing.com/ "  

SecureStoreVariable

This action stores the specified value securely by encrypting it under the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

The variable under which the string data is to be stored.

Yes

String

data

Enter the data to be stored in encrypted mode.

No

String

Example:

SecureStoreVariable              "Password"                               "Encrypt(Abc)"

When the focus is moved away from the data ABC, Qualitia will automatically encrypt the text to "vHpmlfI4R3PQJskt3nuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

CalculateDifferenceInDateAndStore

This action calculates the difference between two specified dates as per the number of days. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

startDate

Enter the start date, that is, the date which is lesser.

Yes

String

startFormat

Enter the start date's date format.

Yes

String

endDate

Enter the end date, that is, the date which is greater.

Yes

String

endFormat

Enter the end date's date format.

Yes

String

Key

Enter a key to store the the difference in date as per the number of days.

        Yes

String

(info) Interval: The interval parameter can have the following values:

Example:
CalculateDifferenceInDateAndStore      "Key"            "D"        "01-Jan-2021"      "28-Feb-2021"

Sleep

This action adds the delay during execution for the given period of time (in seconds).

This action can be used when a particular action takes some time for execution. For instance, after performing an OpenUrl action, some amount of wait can be given till the URL is opened completely.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

seconds

Enter the number of seconds for which you want to wait. 

The default value is 2.

No

String

Example:
Sleep                   "20"

SelectPage

This action helps Qualitia users to move focus from one window/page to another as per the test case requirements. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

windowName

Enter the name of the window which you want to select. You may use "NULL" to select the main window.

No

String

Example:

Select Page                            "Name"

SelectWindowUsingURL

This action selects the window using the URL address or URL pattern specified in the parameters.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

URL

Enter the URL address of the page you want to open.

Yes

String

URL Pattern

Specify whether the URL is patterned or not.
The value of this parameter can be True or False.

No

String

 

While executing a test case or test suite that uses the SelectWindowUsingURL action on a mobile web application, you must enter the appropriate values in UDID and Device Name in the associated execution profile.

Example:

SelectWindowUsingURL                      "www.google.com"                    "False"

ClosePopUpBrowser

This action closes the popup that appears on the web page. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

windowName

Enter the name of the window that you want to close.

Yes

String

Example:
ClosePopUpBrowser                   "viewPage"

PressKeys

This action sends one or more keystrokes to the active window (as if typed on the keyboard).

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter the key which you want to press from the key board. 

Yes

String

Example:

To open the Find dialog on the browser, which is done manually using Ctrl + F.  While using the PressKeys action, the data to be passed is ~^F where ^ means Control. See the list below for the keys and their meaning).

The action returns 0, if the key is pressed successfully else it will return 1 in any other case. 

Note: If a PressKeys action does not execute on an Inactive Screen, refer to PressKeys Action does not Execute on an Inactive Screen.

Important Note:

The data to be passed here is only ^F. However ^ has a special meaning in QAS, it must be preceded with an escape sequence ~. Hence the data passed is written as ~^F.
Make sure to prefix an escape sequence which is a tilda for the following characters which has a special meaning in Qualitia. The characters are {,}, ^, ~
Example:

  1. If key to be sent is {F1}, enter data as ~{F1~}.
  2. To send {TAB}, enter data as ~{TAB~}.
  3. To send {ENTER}, enter data as ~{ENTER~}.

Use the PressKeys action to send keystrokes to applications that have no automation interface. Most keyboard characters are represented by a single keystroke. Some keyboard characters are made up of combinations of keystrokes (CTRL+SHIFT+HOME, for example). To send a single keyboard character, send the character itself as the string argument. For example, to send the letter x, send the string argument "x".

 

You can use PressKeys to send more than one keystroke at a time. To do this, create a compound string argument that represents a sequence of keystrokes by appending each keystroke in the sequence to the one before it. For example, to send the keystrokes a, b, and c, you need to send as "abc". The PressKeys method uses some characters as modifiers of characters (instead of using their face-values). This set of special characters consists of parentheses, brackets, braces, and the:

  • plus sign       "~{+~}",

  • caret             "^", (use with an escape character [~])

  • percent sign "%"

  • tilde       "~"

Enter these characters by enclosing them within braces "{}". For example, to enter the plus sign, enter the string argument "{+}". Brackets "[ ]" have no special meaning when used with PressKeys, but you must enclose them within braces to accommodate applications that do give them a special meaning (for dynamic data exchange (DDE) for example).

  • To send bracket characters, enter the string argument "{[}" for the left bracket and "{]}" for the right one.

  • To send brace characters, enter the string argument "}" for the left brace and "{" for the right one.

  • To send a key combination that includes Ctrl key such as Ctrl + N send "~^n"

Some keystrokes do not generate characters (such as ENTER and TAB). Some keystrokes represent actions (such as BACKSPACE and BREAK). To send these kinds of keystrokes, enter the associated arguments as shown in the following table:

Key

Argument

BACKSPACE

~{BACKSPACE~}, ~{BS~}, or ~{BKSP~}

BREAK

~{BREAK~}

CAPS LOCK

 ~{CAPSLOCK~}

DEL or DELETE

~{DELETE~} or ~{DEL~}

DOWN ARROW

~{DOWN~}

END

~{END~}

ENTER

~{ENTER~} or ~

ESC

~{ESC~}

HELP

~{HELP~}

HOME

~{HOME~}

INS or INSERT

~{INSERT~} or ~{INS~}

LEFT ARROW

~{LEFT~}

NUM LOCK

~{NUMLOCK~}

PAGE DOWN

~{PGDN~}

PAGE UP

~{PGUP~}

RIGHT ARROW

~{RIGHT~}

SCROLL LOCK

~{SCROLLLOCK~}

TAB

~{TAB~}

UP ARROW

~{UP~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

F13

~{F13~}

F14

~{F14~}

F15

~{F15~}

F16

~{F16~}

 

The PressKeys action is not tested on the F13 to F16 keys, which are generally not present on the keyboard.

To send keyboard characters that are comprised of a regular keystroke in combination with a SHIFT, CTRL, or ALT, create a compound string argument that represents the keystroke combination. You can do it by preceding the regular keystroke with one or more of the following special characters:

Key

Arguments

Shift

~+

Ctrl

~^

Alt

~%

(info) When used this way, these special characters are not enclosed within a set of braces.

To specify that a combination of SHIFT, CTRL, and ALT should be held down while several other keys are pressed, create a compound string argument with the modified keystrokes enclosed in parentheses. For example, to send the keystroke combination that specifies that the SHIFT key is held down while:

  • e and c are pressed, enter the string argument "+(ec)".

  • e is pressed, followed by a lone c (with no SHIFT), enter the string argument "+ec".

You can use the PressKeys action to send a pattern of keystrokes that consists of a single keystroke pressed several times in a row. To do this, create a compound string argument that specifies the keystroke you want to repeat, followed by the number of times you want it repeated. To do this, use a compound string argument of the form {keystroke number}. For example, to send the letter "x" ten times, you would send the string argument "~{x 10~}" where you need to ensure that you enter a space between keystroke and number.

  • The only keystroke pattern you can send is the kind that is comprised of a single keystroke pressed several times. For example, you can send "x" ten times, but you cannot do the same for "Ctrl+x".

  • You cannot automate the PRINT SCREEN key ~{PRTSC~} to an application.

  • To send a space, enter the string " ".

StoreDateTimeByZone

This action helps to convert the date and time provided by the user into the expected time zone.

Input Parameters:

Parameter Name

Parameter Description 

Mandatory

Data Type

expectedTimeZoneID

Enter the zone ID in which you want to convert the date and time. Refer to the list below for the complete list of time zones (case-sensitive). 

Yes

String

currentTimeZoneID

Enter the current zone ID in which you are giving the date and time. Refer to the list below for the complete list of time zones (case-sensitive). 

Yes

String

dateTime

Enter the date and time that you want to convert in the expected time zone. 

Yes

String

dateTimeFormat

Enter the format in which you have given date and time format. Refer to the list below for the complete list of supported date and time formats (case-sensitive).

Yes

String

key

Enter the key under which you want to store the date and time of the expected zone. Key value can be retrieved using the key name. 

Yes

String

Example:

StoreDateTimeByZone          “EST”         “IST”      “2018-09-23 12:34:44”          “yyyy-mm-dd hh:mm:ss”       “ESTTime”

  • Result:

End of the execution, this action converts the given time into the expected time zone and stores it in under the key: ESTTime.

List of Zone IDs:

Here is the complete list of supported Zone IDs and their descriptions. Please note that these Zone IDs mentioned herein is case-sensitive and should be used in the upper case only.

ZoneID

Description

EST

Eastern Standard Time 

HST

Hawaii Standard Time 

MST

Malaysia Standard Time 

ACT

Australia/Darwin

AET

Australia/Sydney 

AGT

America/Argentina/Buenos_Aires 

ART

Africa/Cairo

AST

America/Anchorage 

BET

America/Sao_Paulo

BST

Asia/Dhaka 

CAT

Africa/Harare

CNT

America/St_Johns 

CST

America/Chicago

CTT

Asia/Shanghai 

EAT

Africa/Addis_Ababa 

ECT

Europe/Paris

IET

America/Indiana/Indianapolis

IST

Asia/Kolkata

JST

Asia/Tokyo 

MIT

Pacific/Apia 

NET

Asia/Yerevan 

NST

Pacific/Auckland 

PLT

Asia/Karachi 

PNT

America/Phoenix

PRT

America/Puerto_Rico 

PST

America/Los_Angeles 

SST

Pacific/Guadalcanal 

VST

Asia/Ho_Chi_Minh 

List of supported dateTimeFormats:

Here is the complete list of date and time formats and their examples. Please note that these date and time formats mentioned herein are case-sensitive and should be used in the same way as mentioned in the table below. 

Date Time Formats 

Examples

dd-MM-yy 

31-01-12 

dd-MM-yyyy

31-01-2012

MM-dd-yyyy

01-31-2012

yyyy-MM-dd 

2012-01-31

yyyy-MM-dd hh:mm:ss 

2012-01-31 23:59:00 

yyyy-MM-dd hh:mm:ss.SSSZ

2012-01-31 23:59:59.999+0100 

EEEEE MMMMM yyyy HH:mm:ss.SSSZ

Saturday November 2012 10:45:42.720+0100

 

You can create your own combinations and formats using the patterns mentioned here. These patterns mentioned herein are case-sensitive such as entering as dd-mm-yyyy instead of dd-MM-yyyy will result in wrong output. Ensure that you use them in a correct way in order to achieve the desired output. 

StoreSubStringNew

This action stores a sub string of a string into a variable. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

The variable in which the sub-string is to be stored.

Yes

String

sourceString

Enter the string whose sub-string value is to be stored.

No

String

startIndex

Enter the index of the string from where the sub-string is to be fetched.

No

String

endIndex

The number of characters required in the string.

No

String

 

Example:
StoreSubStringNew                   "resultSubString"            "This is a test"                "2"                  "4"

StoreSubStringFromIndexForLength

The action stores the substring of a string from a specific index up to any number of characters that you want. The indexing starts from 1.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable to store the resulted substring.

Yes

String

sourceString

Enter the original string.

Yes

String

startIndex

Enter the index of the character in the original string from where you want to start your substring. The default value is 1.

No

String

length

Enter the number of the characters from the specified startIndex up to which you want to store.

Yes

String

Example:

StoreSubStringFromIndexForLength     "Key"    “Welcome"     “4”      “4”

The variable Key stores the value as come.

StoreStringToInteger

This action converts the provided string to the integer value and stores it into 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 in which you want to store integer value.

Yes

String

Number

Enter the number whose integer value you want to store into the key.

Yes

String

Example:

StoreStringToInteger            "Key"          "20"

StoreStringLength

This action increments the string length by the value specified by the user and stores it into a variable.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

The variable in which the length of the string is to be stored

Yes

String

strMainString

The string whose length is to be stored

No

String

intIncrement

The value by which the length needs to be incremented

No

String

Example:
StoreStringLength                             "length"                      "This is a test"            "3"

CompareString

This action compares two strings without trimming the spaces. The comparison can be either case-sensitive / non case-sensitive. Even a key can be passed as one of the parameters for comparison where the CompareString function will retrieve the value from the key and that value will be compared with expected.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

actualString

Enter the string value that you want to compare. You can pass the key name here enclosed in braces.

No

String

excpectedString

Enter the expected string value against which the actualString will be compared. You can pass the key name here enclosed in braces.

No

String

caseSensitive

Specify the kind of comparison; case-sensitive or case-insensitive.

  • Set True for case-sensitive comparison. 

  • Set False for case-insensitive comparison.
    Note: If you do not specify, by default, True is considered

No

String

 

CompareString           "{key}"           "Cancel"          "True"

Here the CompareString action shall retrieve the value for the key (here Cancel) and compare it with the expected (here Cancel) with case sensitive comparison as True. The action will return 0, if the strings match else it will return 2 if the strings do not match. It will return 1 in any other case (like an error).

PrintMessageinReport

This action helps you to print the desired message in Qualitia test case execution report. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

message

Enter the desired message you want to print into the Qualitia test case execution report.

Yes

String

status

Values for this parameter can be Pass, Fail, Passed, Failed, Defect, and NotExecuted.

Note: The value is not case-sensitive.

No

String

Example:

PrintMessageInReport         "Test case executed successfully without fail."                "Passed"

VerifyStringContainsValue

This action verifies whether a specific substring is present in the main string. Comparison can either be case-sensitive or case-insensitive.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strMainString

Enter the main string in which you want to search substring. You can pass the key name here enclosed in braces.

No

String

strSubstring

Enter the 2nd string value that you want to search. You can pass the key name here enclosed in braces.

No

String

blnCase

Specify the kind of comparison; case-sensitive or case-insensitive.

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison.

No

String

VerifyStringContainsValue      "{mainStrKey}"                               "the action"              "True"

In this case, the VerifyStringContainsValue action shall retrieve the value for the key mainStrKey and compare it with the expected with case sensitive comparison as True.
The action returns  the following values:

  • PASSED if the substring is found in the main string.

  • DEFECT if the substring is not found in the main string.

  • FAILED if the main string or substring is empty.

Empty and null main string as well as substrings are not  verified by this action.

ComparePattern

This action compares the data passed by user and verifies that it matches the pattern specified by the user.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

pattern

Enter the pattern against which the data specified by the user will be verified.

Yes

String

data

Enter the data which will be matched against the pattern specified by the user.

No

String

caseSensitive

Specify the kind of comparison; case-sensitive or case-insensitive.

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison.

Note: The default value is True.

No

String

Example:
Consider a bank application where on adding a user an account number is generated which is unique and consists of alphanumeric characters. The number of characters in that account number is 10 where the first 5 are alphabets and remaining five are numbers.

Suppose the account number is YuIFp96062. If this has to be verified for the pattern mentioned, we can use the action ComparePattern as follows:

  • strPattern -  [a-z]~{0,5~}[0-9]~{5~}

  • strData –  YuIFp96062

  • blnCase -    False

ComparePattern                 “[a-z]~{0,5~}[0-9]~{5~}“                   "YuIFp96062"                  "false"

Here the ComparePattern action shall verify that data mentioned matched the specified pattern .The action will return 0, if the data matches the specified pattern , else it will return 2 if the data does not match the pattern. In any other case it will return 1.

If the pattern is using Qualitia's special characters like {,},/,^ then they should be prefixed with ~.

Special characters and sequences are used in writing patterns for regular expressions. For a complete list of the regular expression syntax visit the VBScript syntax Guide for Regular Expressions.

CompareSubStringPattern

This action verifies whether a string or any of its substring is defined in the desired pattern that you want.

To specify the desired pattern, you can use https://www.regexr.com to validate with the sample strings.

 

Parameter Name

Parameter Description

Mandatory

Data Type

strPattern

Enter the desired pattern for the substring. If you want to match the pattern with whole string, then append '^' at the beginning and '$' at the end of the string.

Yes

String

strData

Enter the string that you want to compare with the desired pattern.

Yes

String

caseSensitive

Specify the kind of comparison:

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison.

Note: The default value is True.

No

String

The action returns the following values:

  • PASSED if the string or any of its substring matches with the desired pattern.

  • DEFECT if the string or any of its substring does not match with the desired pattern..

  • FAILED for any other reason, such as when no value is defined for strData or strPattern parameters.

Example:
CompareSubStringPattern [a-z]~{0,5~}[0-9]~{5~} YuIFp96062 True
In this case, the substring 'p96062' matches with the given case-sensitive pattern. Hence, the action will return Pass.

CompareSubStringPattern ~^[a-z]~{0,5~}[0-9]~{5~}$ YuIFp96062 True
In this case, the action matches the complete string with the specified pattern where it does not match. Hence, the action will return Defect.

VerifyDataType

This action verifies if the data type is numeric or string.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

data

Enter the data to verify.

Yes

String

dataType

The data type against which the data is to be verified.
The value of this is

  • numeric

  • string

Yes

string

Example:

VerifyDataType "4.78" "numeric"
This shall verify if 4.78 is numeric
VerifyDataType "This is a test" "string"
This shall verify if "This is a test" is a string
Anything which is not numeric shall be considered as a string.
Example: "Enter 123", "23/02/20" etc shall be considered as a string.

VerifyDifference

This action verifies the difference between two integer values and validates it with the expected difference value.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Int1

Enter the 1st numerical value to compare. You can pass the key name here enclosed in braces.

No

String

Int2

Enter the 2nd numerical value to compare. You can pass the key name here enclosed in braces.

No

String

expectedDifference

Enter the expected difference between the two numbers.

No

String

Example:
VerifyDifference                       "30"                 "40"               "10"

 

StoreSplitString

This action splits the string based on the specified delimiter character and stores the value that is contained between its previous occurrence of the delimiter into a variable. If there are n delimiters, then there are  (n+1) substrings.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter the key name under which instance of the split string will to be stored.

Yes

String

mainString

Enter the string which you want to split.

No

String

Delimiter

Enter the delimiter which you want to use while splitting the mainString. This can be any alphanumeric or special character.

If the delimiter is a java special character, ensure you escape the character using backslash (\) prior to the delimiter character.

In case there are multiple delimiter characters in the mainString, it stores string backwardly from the specified delimiter up to the next instance of the delimiter character. (see example for more details)

Yes

String

instance

Enter the occurrence of the item which you want to store under the specified key. The instance starts from 1. 

No

String

Example:

StoreSplitString                "spaceKey"         "https://my.atlassian.net/wiki/rest/api/content?spaceKey=QASM=limit=500&start=0"              "="                     "2"

In this example, the delimter is =, as there are multiple occurrences of =in the mainString,,  after this action is executed, the text between 2nd and 1st delimiter character that is QASM will be stored under the specified key spaceKey.

 

MaximizeBrowser

This action maximizes the browser.

This action does not have any parameter. 

Example:

MaximizeBrowser

SelectFrame

This action selects a frame within the current window.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

locator

Enter the locator using which you want to select the frame. This parameter can have the values of the frame's: ID, Name, Xpath, CSS.

No

String

locatorType

Enter which locator type you want to use. It can be ID, Name, xpath, CSS and so on. In order to come out of all the frames, the parameters passed should be empty.

No

String

Example:

SelectFrame                        "mainFrame"               "name"

SelectFrameUsingUrl

This action is used to select a frame irrespective of the frame hierarchy. The frame can be either be an iframe or a normal frame, which are defined in html by <iframe> and <frame> tag respectively.

To pass the URL, do one of the following:

  • Set the StringisUrlPattern parameter to false to pass the exact URL of the frame that you want to select.

  • Set the StringisUrlPattern parameter to True to pass regex pattern for a particular URL.

In both cases, if the given URL has multiple frames, the first frame in the frame hierarchy is selected. If the frame URL does not exist, the context switches to either the first frame on the page, or the main document if the page contains iframes.

Parameter Name

Parameter Description

Mandatory

Data Type

String URL

Enter the  URL of the frame.

No

String

StringisURLPattern

It takes the value True or false denoting whether URL is regex pattern or exact url.

  • Set True for if  URL is a regex pattern

  • Set False for URL is not a regex pattern

No

String

Example

The SelectFrameUsingUrl action will select first frame from the frame hierarchy which is found as per the regex pattern.

StoreCurrentDateInFormat

This action stores the current date in the specified format under the key name. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Format

Enter the format which you want to use to save the date. Use DD for day, MM for month and YYYY for year. 
For example: dd/MM/yyyy , MMM/dd/yyyy , dd-MM-yyyy etc 
dd = day 
MM = month represented as 01,02,03 etc 
MMM = month represented as Jan. Feb, Mar etc 
yyyy = year

Yes

String

key

Enter the key name under which the current date will be stored.

Yes

String

Example:
StoreCurrentDateInFormat                             "MM-dd-yyyy"                "currentDateKey"

StoreDateInFormat

This action stores the date provided by the user in a specific format under the key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

date

The date which needs to be stored in the specified format.

Yes

String

Format

Enter the format using which you want to save the date. Use DD for day, MM for month and YYYY for year.

For example: dd/MM/yyyy , MMM/dd/yyyy , dd-MM-yyyy, and so on.
dd = day 
MM = month represented as 01,02,03 etc 
MMM = month represented as Jan. Feb, Mar etc 
yyyy = year

Yes

String

resultFormat

Format in which the date given by the user needs to be stored.

Yes

String

key

Enter the key name under which the new result will be stored.

Yes

String

Example:
StoreDateInFormat                      "30/Jan/2009"                    "dd/MMM/yyyy"               "dd-MMM-yyyy"             "Datekey"

TrimAndStoreText

This action trims the preceding and succeeding spaces and stores the resulting string in the given key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strText

The string which has to be trimmed.

Yes

String

strKey

The key in which result is to be stored.

Yes

String

 

Example:
TrimAndStoreText                "     John Doe       "           "FullName"

Suppose, you give the strText as "    John Doe    " to store the final string inside the key "FullName". End of the execution, John Doe  will be stored in the key FullName.

TrimAndCompareString

This action compares two strings. The comparison can be either case-sensitive / non case-sensitive. Even a key can be passed as one of the parameters for comparison where the TrimAndCompareString function will retrieve the value from the key and that value will be compared with expected. The spaces of both the strings are trimmed before comparing.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

first-string

First string for comparison

No

String

secondString

Second string for comparison

No

String

CaseSensitive

True for case-sensitive comparison

False for case-insensitive comparison.

No

String

Example:

TrimAndCompareString      “Hello “     “ hello ”    “True”

VerifyDates

This action performs comparisons between two dates for various operations (equality, inequality, greater than, less than).

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

actualDate

Enter the actual date which need to be verified. 

Yes

String

actualDateFormat

Enter the format of the actual date provided earlier.

Yes

String

expectedDate

Enter the expected date against which you want to verify the actual date. 

Yes

String

expectedDateFormat

Enter the format of the expected date provided earlier.

Yes

String

operation

Specify the operation to be performed between the first and second dates.

  • Use < to verify that the first date is less than (comes before) the second date.

  • Use > to verify that the first date is greater than (comes after) the second date.

  • Use == to verify that the dates are equal.

  • Use != to verify that the dates are unequal.

No

String

Example:

The result of this action shall be True or false depending on the operation performed.

VerifyDates                            "12-Jun-2008"                     "dd-MMM-yyyy"                          "04/12/2008"                      "dd/MM/yyyy"               "<"

 

No macro found named "DateTimeFormatSupported" on page "(8.5.X) General Web Actions" in space "QASNew".

If you're experiencing issues please see our Troubleshooting Guide

ChangeCaseAndStore

This action changes the case of the provided string and stores the final value into 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 in which you want to store the updated string.

Yes

String

InputString

Enter the string whose case you want to change.

Yes

String

Case

Value for this parameter can be as follows:

  • Set Upper to change the case of the string to upper case.

  • Set Lower to change the case of the string to lower case.

Yes

String

Example:

ChangeCaseAndStore                "Key"               "Qualitia"             "Upper"

ChangeDateAndStore

This action modifies the day/month/year by the number specified by the user and stores the resulting date under the specified key in the same format as the input date. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

date

Enter the date that needs to be updated.

Yes

String

format

Enter the format of the date given by the user.

Yes

String

dayValue

Enter the value by which you want to increase/decrease the day. For example; "1", "-3".

Yes

String

monthValue

Enter the value by which you want to increase/decrease the month. For example; "1", "-3".

Yes

String

yearValue

Enter the value by which you want to increase/decrease the year. For example; "1", "-3".

Yes

String

key

Enter the key name under which the updated date will be stored. 

Yes

String

Example:
To change date from 1st jan 2007 to 15 feb 2007 user can use 2 ways

  1. Increment only the day value
    dayValue = 45, monthValue = 0 , yearValue = 0
    E.g.- ChangeDateAndStore                      "01-01-2007"                 "dd-MM-yyyy"              "45"             "0"               "0"         "key"

  2. Increment the complete date
    dayValue = 14, monthValue = 1 , yearValue = 0
    E.g.- ChangeDateAndStore                      "01-01-2007"                 "dd/MM/yyyy"              "14"             "1"               "0"         "key"

Hence the user can either give the exact end date or can give the no of days, months or years by which the date needs to be changed.

CalculateDifferenceInDatesAndStore

This action calculates the difference in days between the two specified dates and stores the difference under the specified key. The key value can be used using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

startDate

Enter the start date to compare.

Yes

String

startformat

Enter the date format of the start date.

Yes

String

endDate

Enter the end date to compare.

Yes

String

endFormat

Enter the date format of the end date.

Yes

String

key

Enter the key name under which the difference (in days) will be stored. 

Yes

String

Example:
CalculateDifferenceInDatesAndStore                             "24-Jan-2007"                    "dd-MMM-yyyy"                     "01/26/2007"                      "MM/dd/yyyy            "diffKey"

VerifyDialogExistence

This action verifies if any dialog of the type alert/prompt/confirmation exists on the browser.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Value of this parameter can be True or false.

  • Set True if you want to check for the presence.

  • Set False if you want to check for the absence.

No

String

Example:
VerifyDialogExistence                       "True"

AcceptDialog

This action clicks the OK button on the alert/prompt/confirmation pop up.

This action does not have any parameter.

Example:
AcceptDialog

DismissDialog

This action cancels the alert/prompt/confirmation pop up.

This action does not have any parameter.

Example:
DismissDialog

StoreDialogText

This action stores the message from the alert/prompt/confirmation pop up 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 you want to save the message.

Yes

String

Example:

StoreDialogText               "message"

ExecuteFile

This action executes the batch file specified by the user.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

batchFile

The absolute path to the batch file to be executed. Path should not have whitespace.

Yes

String

Example:
ExecuteFile                     "C:\test\batchfile1.bat"

AttachFile

This action sets a file path in the file object type in html. This action is applicable only for desktop web application.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

fileInputlocator

Enter the locator of the input box where the file is to be selected.

Yes

String

locatorType

Enter the type of locator used for the locator of the file input object. 
This could be Id, xpath, name, CSS.

Yes

 String

filePath

Enter the absolute or relative path of the file. 

Yes

String

Example:

AttachFile                    "fileBox"                "id"                 "c:/Folder/test.txt"

 

This action is designed to upload files from the local directory when executing the test case. In case your test execution environment is other than Local, such as Remote, Sauce, Perfecto, and so on, files will be uploaded from where you initiate the test case execution.
Also, execution of this action highly depends on the browser and driver version you are using.

For example: On Sauce Labs, this action found working seamlessly on Google Chrome version 60 and below and Mozilla Firefox version 47 and below with their default drivers. If the Google Chrome browser version is 61 to 64, you must use chromedriver version 2.29 for this action to work. This action does not work with Mozilla Firefox version 48 and above, Internet Explorer, and Safari browsers.

These findings are tested and verified at the time of documenting this information and are subject to change based on the changes made to the respective browser and driver versions.

 If you want to upload a file using an object, refer to AttachFile action as described in WebFile Actions.

ExecuteQueryAndStoreInFile

This action executes data manipulation queries like select and stores the result into a file.

The file types supported are xml, xls, and txt. The valid extensions are

  1. For text file - .txt

  2. For xml file- .xml

  3. For excel file- .xls

The Qualitia supports querying on the following database types:

  • MySql 5.1

  • Oracle 10g

  • MS Access

  • SQL Server 2008

If this action fails upon execution, refer to  Actions Related to DB Failed upon Execution.

Connection to different databases 

  1. Mysql:

 
a. Driver - "com.mysql.jdbc.Driver" 
b. Connection url - "jdbc:mysql://localhost:portNo/databasename?useUnicode=True&characterEncoding=utf8
i. Databasename -is the mysql database to which the user wishes to connect 

  1. Oracle:

 
a. Driver - "oracle.jdbc.driver.OracleDriver" (case-sensitive)
b. Connection url - "jdbc:oracle:thin:@servername or ip:portNo:Databasename
i. Servername -is the name of the server .If the server is on local system, the server name is localhost. If the server is on remote system, the ip address of the remote server can be used. 
ii. portNo – is the port which shall listen the database connections. The default port for oracle is 1521. If the user has configured a specific port for listening, then that port number should be used here. 
iii. Databasename is the oracle database to which the user wishes to connect 

  1. SQLServer:

 
a. Driver - "com.microsoft.sqlserver.jdbc.SQLServerDriver" 
b. Connection url - "jdbc:sqlserver://servername/ip:port;database=databasename;" 
i. Servername -is the name of the server .If the server is on local system, the server name is localhost. If the server is on remote system, the ip address of the remote server can be used. 
ii. portNo – is the port which shall listen the database connections. The default port for oracle is 1433. If the user has configured a specific port for listening, then that port number should be used here. 
iii. Databasename is the sql server database to which the user wishes to connect 

  1. MSAccess using dsn:

 
a. Driver - "sun.jdbc.odbc.JdbcOdbcDriver" 
b. Connection url - "jdbc:odbc:dsn_name 
i. dsn_name -is the name of the dsn configured on the system . If multiple users are accessing the same dsn, then it needs to be configured on a shared path instead of local system path.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Driver

Enter the driver for the database.

Yes

String

url

Enter the connection string to connect to the database.

Yes

String

username

Enter the user name to connect to the database.

Yes

String

Password

Enter the password to connect to the database.

Yes

String

Query

Enter the ddl query that needs to be executed.

Yes

String

File

Enter the absolute path of the file in which the results of the database query need to be stored.

Yes

String

Example
ExecuteQueryAndStoreInFile "oracle.jdbc.driver.OracleDriver" "jdbc:oracle:thin:@localhost:1521:orcl" "scott" "tiger" "select * from test_table where id = 100" "C:\DBResults\XML\ORACLE\Result.xml"

ExecutQueryAndStoreInKey

This action executes data definitions queries like update, delete and stores the result into a key.

The Qualitia supports querying on the following database types:

  • MySql 5.1

  • Oracle 10g

  • MS Access

  • SQL Server 2008

If this action fails upon execution, refer to  Actions Related to DB Failed upon Execution.

Perform the following steps:

  1. From the Qualitia client, select the associated project.

  2. Click Settings > Project Configuration > Manage Dependent jar.

  3. Enter the location of DB jar.

  4. Click OK.

Connection to different databases 

  1. Mysql:

 
a. Driver - "com.mysql.jdbc.Driver" 
b. Connection url - jdbc:mysql://localhost:portNo/databasename?useUnicode=True&characterEncoding=utf8
i. Databasename -is the mysql database to which the user wishes to connect 

  1. Oracle:

 
a. Driver - "oracle.jdbc.driver.OracleDriver" 
b. Connection url - "jdbc:oracle:thin:@servername or ip:portNo:Databasename
i. Servername -is the name of the server .If the server is on local system, the server name is localhost. If the server is on remote system, the ip address of the remote server can be used. 
ii. portNo – is the port which shall listen the database connections. The default port for oracle is 1521. If the user has configured a specific port for listening, then that port number should be used here. 
iii. Databasename is the oracle database to which the user wishes to connect 

  1. SQLServer:

 
a. Driver - "com.microsoft.sqlserver.jdbc.SQLServerDriver" 
b. Connection url - "jdbc:sqlserver://servername/ip:port;database=databasename;" 
i. Servername -is the name of the server .If the server is on local system, the server name is localhost. If the server is on remote system, the ip address of the remote server can be used. 
ii. portNo – is the port which shall listen the database connections. The default port for oracle is 1433. If the user has configured a specific port for listening, then that port number should be used here. 
iii. Databasename is the sql server database to which the user wishes to connect 

  1. MSAccess using dsn:

 
a. Driver - "sun.jdbc.odbc.JdbcOdbcDriver" 
b. Connection url - "jdbc:odbc:dsn_name 
i. dsn_name -is the name of the dsn configured on the system . If multiple users are accessing the same dsn, then it needs to be configured on a shared path instead of local system path.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Driver

Enter the driver for the database.

Yes

String

url

Enter the connection string to connect to the database.

Yes

String

username

Enter the user name to connect to the database.

Yes

String

Password

Enter the password to connect to the database.

Yes

String

Query

Enter the dml query that needs to be executed.

Yes

String

key

Enter the key in which the result of the database query need to be stored.

Yes

String

Example:
ExecuteQueryAndStoreInKey "oracle.jdbc.driver.OracleDriver" "jdbc:oracle:thin:@localhost:1521:orcl" "scott" "tiger" "delete from test_table where id = 100" "Resultkey"

CompareTabularResults

This action compares the database results in two files and displays only the difference in an Microsoft or a kingsoft Excel sheet. A link is generated in the log file. On clicking the link, the excel sheet opens in which the difference in the data is displayed. This action compares the following file types which contain DB results. These files contain the results after executing the queries using the actions "ExecuteQueryAndStoreInFile" or "StoreTableData". The supported file extension types are : txt, xml and xls.

  1. text and text

  2. text and excel

  3. text and xml

  4. xml and xml

  5. xml and excel

  6. excel and excel

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

sourceFile

Enter the source file to be used for the comparison. 

Yes

String

targetFile

Enter the target file against which you want to compare the source file.

Yes

String

resultFileType

The file type in which the difference between the two results need to be displayed. The file type supported is: 
MSExcel 

No

String

Example
CompareTabularResults             "C:\DBResults\XML\ORACLE\Result.xml"                 "C:\DBResults\Excel\ORACLE\Result.xls"                     "MSExcel"

ComputeExpression

This action evaluates mathematical, relational, logical operations and stores the result under the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expression

The expression to be evaluated

Yes

String

strKey

The key under which the result of the evaluation will be stored.

Yes

String

Example:

Mathematical Expression
ComputeExpression                "24*2+4"              "Result"

Example:

Relational Expression
ComputeExpression               "10*2<30"             "Result"

Example:

Logical Expression
ComputeExpression             "10*2+1>19&10*2+2<23'"     "Result"

CompareArray

This action compares two arrays for equality.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

actualArray

Enter the array which you want to compare. Array items are separate by carat (^) sign.

No

Array

excpectedArray

Enter the expected array against which you want to com[are the actual array.

Array items are separate by carat (^) sign.

No

Array

match

This parameter specifies the type of comparison to be done. It can be one of the following: 

  • Exact – This will compare the items of the array for exact match that is size of the two arrays should match. The sequence in which the items occur in the arrays should match. This is a one to one comparison. 

  • Partial- This compares if the second array is a sub-list of the first. The sub-list items in the second array need not be in the same sequence as they appear in the first array. However, it is not vice versa, that is, it will not check if the first array is a sub-list of the seconds array. In this case, the action will fail.

No

String

Example :
CompareArray "1^2^3^4" "1^2^3^4"             "exact"
CompareArray "1^2^3^4^5^6" "2^1^3^4"      "partial"

StoreWindowHandle

This action fetches the handle (identifier) of a window and stores under the specified key.  This key can the be used in action like SelectPage and ClosePopupBrowser to work on the specific page. This action can be used when the name of the window on which user needs to work on is not known.

Also, this action will have to be used immediately after every action which results in opening a new window. Only then user will be able to work on the new opened window. Thus, immediately after every action which opens a new window, this action will have to be used in order to fetch the identifier of the new window.

This action has to be used for every window of the application. For more information about this, please refer to the knowledge base here

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter the key name to store the window handle.

Yes

String

Example: 
Object1                                   Click 
StoreWindowHandles            "new window" 
SelectPage                              "{new window}" 
EditObjectOnNewPage           Set                 Testing 
In the example above, on clicking on object1 a new window is opened on which actions need to be performed.

Use the action StoreWindowHandles to fetch the handle of the new window opened. Use the SelectPage action to select the window. Then user can work on an object present on the new page.

Also, when the action OpenUrl is used, user will have to store the handle on this main application window.

Example:

OpenUrl                                 "http://www.google.com"
StoreWindowHandle            "mainapplicationWindow"

ExitTask

This action skips the execution of the next step and continue executing the next task. 

This action is not available for test case level step.

This action does not have any parameter.

Example:

ExitTask

ExitTCIteration

This action skips the execution of the current iteration of test case and execute next iteration. In case of a single TC Iteration the test case execution will stop.

This action does not have any parameter.

Example:

ExitTCIteration

ExitSuite

This action stops the execution of the test suite and no further test cases will be executed.

This action does not have any parameter.

Example:

ExitSuite

VerifyLinkOnPage

This action verifies if there is any hyperlink exists on the page.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Link

The locator of the link to be verified. This is the inner text of the link.

Yes

String

Example:
VerifyLinkOnPage                    "AdvancedSearch"

StoreChildCount

This action stores the child count for the specified locator. The action counts the last element in the Xpath which are placed inside the parent hierarchy. The child elements to be counted can be immediate children/descendants. The user should pass relevant Xpath to achieve children/descendants count.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type 

locator

The xpath of the object whose child count is to be retrieved.

It is mandatory that the input should be an xpath locator. This action will fail for any other locator type.

Yes

String

key

Enter the key name under which the count will be stored.

Yes

String

Example
StoreChildCount                      "//table[@id='12']/tbody/tr/td/div"         "Key"

DownloadFile

This action clicks the link or element that opens a download window, which is used to download the files.  You need to handle the action externally as it does not wait until the file is downloaded.

 Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.

  • Select the Offline Suite and the associated execution profile.

  • Click Qualitia Settings > General AutoIT Path.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validate whether the folder exist

Yes

String

Filename

The filename of the downloadable file, to be given in case the user requires to give a specific name and not depend on the default name of the file. In case, the file already exists, similar window like below will appear. Such windows are not handled by the action. In case, the user does not provide this data, the action will pick the default file name available while downloading.

No

String

locator

Enter the locator value.

Yes

String

locatorType

Enter which locator type you want to use. It can be ID, Name, xpath, CSS and so on.

Yes

String

 

Example:

 

 

 

Example:  DownloadFile               "C:/ProgramData"           "Qualitia"       "DOWNLOAD SAMPLE DOC FILE"       "Link" 

RefreshPage

This action simulates the refresh operation on the currently selected page.

This action does not have any parameter. 

Example:

RefreshPage

DeleteCookiesOnCurrentDomain

This action deletes all the cookies that are visible to the current domain. 

This action does not have any parameter. 

If the page is www.google.co.in and the user runs the above action, then all the cookies created by www.google.co.in will be deleted.

If there is a link in www.google.co.in and on clicking, it navigates to www.apple.com.

Again , when the user runs the above action, then all the cookies create by www.apple.com will be deleted.

Reiterating, to delete www.google.co.in cookies, the application needs to be in www.google.co.in domain.

This action will automatically, pick up the current domain and will delete cookies of that domain. The user just needs to make sure that he runs this action only in the domain for which the cookies are to be deleted.

Note: In HTML, due to security reasons, the only website that can read/delete a cookie is the one that creates it.

Example:
DeleteCookiesOnCurrentDomain

AcceptDialogAndStoreMessage

This action accepts the dialog appeared on the Web page and stores the message under the specified key. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key in which the message will be stored.

Yes

String

Example:
AcceptDialogAndStoreMessage                  "AlertMessage"

ValidateSyntaxInFile

This action validates the data given in the specified JSON or XML file.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute path to the JSON/XML file on which you want to validate the data.

Yes

String

 

Example: 

ValidateSyntaxInFile           "C:\Users\Qualitia\Cust_Details.json" 

End of the execution, if the data from the specified file is valid, action will pass, else action will fail. 

WriteToBuildProperty

This action writes a user defined property along with its value to qer.properties file. This customized information can be used in email notifications sent by Jenkins provided all the required email specific settings are done there in Jenkins.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

propertyName

Property name to be written in qer.properties file

Yes

String

propertyValue

Property value to be written in qer.properties file

Yes

String

Example:
WriteToBuildProperty             "propertyName"                 "propertyValue"

WindowsAuthenticationLogin

This action is required to add authentication details in the window to log into the application.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.

  • Select the Offline Suite and the associated execution profile.

  • Click Qualitia Settings > General AutoIT Path.

 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the URL to the web application.

Yes

String

Username

Enter the username to sign in.

Yes

String

Password

Enter the password to sign in.

Yes

String

 

Example:

WindowsAuthenticationLogin                      "http://www.abc.com"               "testuser1"        "passwduser1"

NoOps

This is a placeholder action and cannot be executed. Qualitia selects this action for the steps present under the activity when auto-populating test case.

You are requested to replace this action with Qualitia executable action.

This action does not have any parameters. 

When executing test cases with this action, test cases will be failed to notify Qualitia users about replacing such actions.

MinimizeWindow

This action minimizes the window.

This action does not have any parameter. 

Example:

MinimizeWindow

SetPageLoadTimeout

This action sets the page load timeout when executing test cases. The time set here overrides the Page Timeout set in the associatedInput Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeoutinSeconds

Enter the expected timeout to load the page.  

Yes

String

Example:

SetPageLoadTimeout             "20"

StorePageSource

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

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyPageSource

Enter the key name to store the page source in.   

Yes

String

Example:

StorePageSource             "PageSource"

StoreWindowHandleAtIndex

This action fetches the handle (identifier) of the specified window in the index and stores under the specified key.  This key can the be used in action like SelectPage and ClosePopupBrowser to work on the specific page. This action can be used when the name of the window on which user needs to work on is not known.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter the key name to store the window handle.

Yes

String

index

Enter the index of the page whose handle you want to store.

Yes

String

Example : 

StoreWindowHandleAtIndex              "Key"                   "4"

SwitchWebExecutionPlatform

This action changes the current Web execution platform from Desktop to Mobile. When used, web application test case will run on specified platform.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Platform

Platform to run web application on. Supported platforms are "Desktop" and "Mobile".

Yes

 String

Example:

SwitchWebExecutionPlatform                        "Mobile"

WaitForNumberofWindowsToBe

This action waits until the number of open windows reaches the count specified in the parameter. You may use polling interval and timeout, if required.

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumber

Enter expected number of windows.   

No

String

timeOut

Enter the timeout (in seconds) to wait. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check whether the specified count has reached. 

No

String

keyNumOfWindows

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfWindowsToBe       "3"         "10"      "500"       "Key"     "Defect"

SetWindowSize

This action sets the window size based on the parameters provided (height and width).

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

width

Enter the expected width of the window in pixel. 

Yes

String

height

Enter the expected height of the window in pixel. 

Yes

String

 

This action has some undefined behavior when values provided in the parameter are outside the allowed range depending on the device resolution or browser driver being used.

Example:

SetWindowSize          "1344"             "689"

StoreWindowSize

This action stores the current size of the window under the specified keys. These key values can be retrieved using the key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

KeyHeight

Enter the key name to store the height of the window.

Yes

String

KeyWidth

Enter the key name to store the width of the window.

Yes

String

Example:

StoreWindowSize          "Height"             "Width"

SetWindowPosition

This action sets the position of the console window as per the specified position.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

xPosition

Enter the x coordinate of the position to set.

Yes

String

yPosition

Enter the y coordinate of the position to set.

Yes

String

Example:

SetWindowPosition          "123"             "232"

StoreWindowPosition

This action stores the current position of the window under the specified keys. These key values can be retrieved using the key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the X coordinate.

Yes

String

keyYPosition

Enter the key name to store the Y coordinate.

Yes

String

Example:

StoreWindowPosition          "XCordinateValue"             "YCordinateValue"

SetFullScreen

This action sets the browser in the full screen mode. 

This action does not have any parameter.

Example:

SetFullScreen

ClickAndHold

This action clicks (without releasing) at the current mouse location.

This action does not have any parameter.

Example:

ClickAndHold

DoubleClick

This action performs a double click action at the current mouse location.

This action does not have any parameter. 

Example:

DoubleClick

RightClick

This action performs a right-click action at the current mouse location.

This action does not have any parameter.

Selenium requires a click action to be performed in case this (RightClick) action is used two times in a single test case. In case you do not use any click action between two RightClick actions, the second instance of the RightClick will not be visible.

 

Example:

RightClick

SelectFrameByIndexWhenAvailable

This action waits for the specified frame to appear on the page and selects when it is available. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

frameIndex

Enter the index of the frame which you want to wait and select for. Index starts at 0.   

No

String

timeOut

Enter the timeout (in seconds) to wait for the frame. 

No

String

pollingInterval

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

No

String

key

Enter the key name under which the status of this step will be stored. 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:

SelectFrameByIndexWhenAvailable       "3"         "10"      "500"       "Key"     "Defect" 

WaitForJavaScriptReturnsValue

This action runs the parameterized JavaScript code until it returns the value. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

JavaScriptString

Enter the JavaScript code to run. 

No

String

keyReturnValue

Enter the key under which the javascript return value will be stored. The key value can be retrieved using the key name. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the value. 

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForJavaScriptReturnsValue       "return eval('2-1');"    "key"      "10"      "500"       "Key"     "Defect"  

WaitForJavaScriptThrowsNoExceptions

This action runs the parameterized JavaScript code until it throws the execption. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

JavaScriptString

Enter the JavaScript code to run. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the exception. 

No

String

pollingInterval

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

No

String

keyJSThrowsExceptionStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForJavaScriptThrowsNoExceptions       ""          "10"      "500"       "Key"     "Defect"  

WaitForTitleContains

This action waits for the web page title to contain expected partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Input Parameters: 

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected partial value of the web page title.

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleContains

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleContains      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForTitleNotContains

This action waits until the web page title changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected partial value which should not be in the web page title. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleNotContains      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForTitleToBe

This action waits for the web page title to contain exact expected parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Input Parameters: 

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected exact value of the web page title.

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleToBe      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForTitleNotToBe

This action waits until the web page title changes to other than the parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected exact value which should not be in the web page title. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleNotToBe      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForURLContains

This action waits for the web page URL to contain expected partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the expected partial value of the web page URL. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyURLContains

Enter the key name under which the status of this step will be stored. 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:

WaitForURLContains      "OAuth%9"          "5"          "500"        "Key"        "Defect"

WaitForURLNotContains

This action waits until the web page URL changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the expected partial value which should not be in the web page URL. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyURLNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForURLNotContains      "OAuth%9"          "5"          "500"        "Key"        "Defect"

WaitForURLToBe

This action waits for the web page URL to contain exact expected parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the expected the web page URL. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected URL. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected URL before exhausting timeout. 

No

String

keyURLToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForURLToBe      "https://google.co.in"          "5"          "500"        "Key"        "Defect"

WaitForURLNotToBe

This action waits until the specified web page URL value changes to other than the parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the URL which should not be the web page URL.

No

String

timeOut

Enter the timeout (in seconds) to wait for the URL to change. 

No

String

pollingInterval

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

No

String

keyURLNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForURLNotToBe      "https://google.co.in"          "5"          "500"        "Key"        "Defect"

WaitForURLPattern

This action waits until the specified web page URL value changes to the parameterized regular expression pattern. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

urlRegx

Enter the expected pattern for the URL. Pattern should be regular expression. Step fails in case the pattern is invalid.

No

String

timeOut

Enter the timeout (in seconds) to wait for the URL to change. 

No

String

pollingInterval

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

No

String

keyURLPattern 

Enter the key name under which the status of this step will be stored. 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:

WaitForURLPattern      "http[s]:\/\/www\.mysite\.com.*"          "5"          "500"        "Key"        "Defect"

WaitForAlertAndSendText

This action waits for the page to prompt an alert. After the alert is prompted, you can send the text specified in the parameter. You may specify the timeout and polling interval, if required.

After adding the required text, you can use the AcceptDialog or WaitForAlertAndSpecifyBehavior to continue test case execution on the main window.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

textToSend

Enter the text you want to send in the alert. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the alert. 

No

String

pollingInterval

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

No

String

keyAlertAvailable

Enter the key name under which the status of this step will be stored. 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:

WaitForAlertAndSendText      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForAlertAndSpecifyBehavior

This action waits for the web page to prompt an alert. After the alert is prompted, you can either accept the dialog or dismiss the dialog giving appropriate values in the parameters. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

acceptOrDismiss

Values for this parameter can be: accept or dismiss.

  • Set accept if you want to accept the dialog. 

  • Set dismiss if you want to dismiss the dialog.  

No

String

timeOut

Enter the timeout (in seconds) to wait for an alert. 

No

String

pollingInterval

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

No

String

keyAlertAvailable

Enter the key name under which the status of this step will be stored. 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:

WaitForAlertAndSpecifyBehavior      "accept"          "5"          "500"        "Key"        "Defect"

MinimizeWindow

This action minimizes the window.

This action does not have any parameter. 

Example:

MinimizeWindow

SetPageLoadTimeout

This action sets the page load timeout when executing test cases. The time set here overrides the Page Timeout set in the associatedInput Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeoutinSeconds

Enter the expected timeout to load the page.  

Yes

String

Example:

SetPageLoadTimeout             "20"

StorePageSource

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

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyPageSource

Enter the key name to store the page source in.   

Yes

String

Example:

StorePageSource             "PageSource"

StoreWindowHandleAtIndex

This action fetches the handle (identifier) of the specified window in the index and stores under the specified key.  This key can the be used in action like SelectPage and ClosePopupBrowser to work on the specific page. This action can be used when the name of the window on which user needs to work on is not known.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter the key name to store the window handle.

Yes

String

index

Enter the index of the page whose handle you want to store.

Yes

String

Example : 

StoreWindowHandleAtIndex              "Key"                   "4"

SwitchWebExecutionPlatform

This action changes the current Web execution platform from Desktop to Mobile. When used, web application test case will run on specified platform.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Platform

Platform to run web application on. Supported platforms are "Desktop" and "Mobile".

Yes

 String

Example:

SwitchWebExecutionPlatform                        "Mobile"

SetWindowSize

This action sets the window size based on the parameters provided (height and width).

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

width

Enter the expected width of the window in pixel. 

Yes

String

height

Enter the expected height of the window in pixel. 

Yes

String

 

This action has some undefined behavior when values provided in the parameter are outside the allowed range depending on the device resolution or browser driver being used.

Example:

SetWindowSize          "1344"             "689"

StoreWindowSize

This action stores the current size of the window under the specified keys. These key values can be retrieved using the key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

KeyHeight

Enter the key name to store the height of the window.

Yes

String

KeyWidth

Enter the key name to store the width of the window.

Yes

String

Example:

StoreWindowSize          "Height"             "Width"

SetWindowPosition

This action sets the position of the console window as per the specified position.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

xPosition

Enter the x coordinate of the position to set.

Yes

String

yPosition

Enter the y coordinate of the position to set.

Yes

String

Example:

SetWindowPosition          "123"             "232"

StoreWindowPosition

This action stores the current position of the window under the specified keys. These key values can be retrieved using the key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the X coordinate.

Yes

String

keyYPosition

Enter the key name to store the Y coordinate.

Yes

String

Example:

StoreWindowPosition          "XCordinateValue"             "YCordinateValue"

SetFullScreen

This action sets the browser in the full screen mode. 

This action does not have any parameter.

Example:

SetFullScreen

ClickAndHold

This action clicks (without releasing) at the current mouse location.

This action does not have any parameter.

Example:

ClickAndHold

DoubleClick

This action performs a double click action at the current mouse location.

This action does not have any parameter. 

Example:

DoubleClick

RightClick

This action performs a right-click action at the current mouse location.

This action does not have any parameter.

Selenium requires a click action to be performed in case this (RightClick) action is used two times in a single test case. In case you do not use any click action between two RightClick actions, the second instance of the RightClick will not be visible.

 

Example:

RightClick

SelectFrameByIndexWhenAvailable

This action waits for the specified frame to appear on the page and selects when it is available. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

frameIndex

Enter the index of the frame which you want to wait and select for. Index starts at 0.   

No

String

timeOut

Enter the timeout (in seconds) to wait for the frame. 

No

String

pollingInterval

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

No

String

key

Enter the key name under which the status of this step will be stored. 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:

SelectFrameByIndexWhenAvailable       "3"         "10"      "500"       "Key"     "Defect" 

AnswerForNextDialog (Deprecated)

This action sets the input as the answer for the next prompt. After setting the answer, webdriver by default may cancel the prompt.

In order to accept and submit your input in the prompt, this action should be used followed by the action "AcceptDialog".

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

answer

Enter the input which you want to set in the next prompt.

Yes

String

Example:

AnswerForNextDialog           "Hello"

StoreSubString (Deprecated)

This action stores a substring of a string into a variable. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

The variable in which the sub-string is to be stored.

Yes

String

sourceString

Enter the string whose sub-string value is to be stored.

No

String

startIndex

Enter the index of the string from where the sub-string is to be fetched.

No

String

endIndex

The number of characters required in the string.

No

String

 

Example:
StoreSubString                   "resultSubString"            "This is a test"                "2"                  "4"

StoreRandomAlphanumericString

This action generates any random alphanumeric string for a specific length that you want and stores the random value for the specified key. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the random text.

Yes

String

Length

Specify the number of characters of the string you want to generate and store under the key name.

Yes

String

Example:

StoreRandomAlphanumericString               "Key"                       "10"

StoreRoundNumber

This action stores values specified by the user by rounding them off to the nearest whole number. The rounded off value stored in the key can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name in which you want to store rounded value.

Yes

String

Number

Enter the number whose value you want to store into the key.

Yes

String

 

Example:

StoreRoundNumber           "key"                 "6.43"

  • In this case, 6 will be stored into the key.

StoreRoundNumber           "key"                "6.55"

  • In this case, 7 will be stored into the key.

StoreRandomNumber

This action picks up any random number from the specified range and stores that number in the specified key. The key value can be retrieved using the key name.

Number can be duplicated, if you use this action multiple times in a single test case.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

MinNumber

Enter the minimum number.

Yes

String

MaxNumber

Enter the minimum number.

Yes

String

strKey

Enter the key name under which you want to store the random number.

Yes

String

 

Example:

StoreRandomNumber        “123”         “890”        “Key”

StoreStringConcat

This action concatenates (combines) two strings specified by the user and stores into the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

String1

Enter the string first string.

Yes

String

String2

Enter the another string.

Yes

String

Key

Enter the key name under which you want to store the combined value.

Yes

String

 

Example:

StoreStringConcat                "String1"          "String2"        "Key"

StoreRandomString

This action generates and stores any random string of the specified length into the 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 you want to store the random text.

Yes

String

Length

Specify the number of characters of the string you want to generate and store under the key name.

Yes

String

Example:

StoreRandomString               "Key"                    "23"

StoreStringFromRight

This action stores the specified number of characters from the right side of the given string. The stored 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 you want to store the specified number of characters.

Yes

String

InputString

Enter the input string from which you want to store the characters.

Yes

String

Length

Specify the number of characters you want to store under the key name. Enter 0 if you want to store an empty string.

Yes

String

 

Example:

StoreStringFromRight         "Key"      "John Doe"         "3"        

In this case, the last three characters, that is, Doe will be stored under the key name.

StoreStringFromLeft

This action stores the specified number of characters from the left side of the given string. The key value can be retrieved using the key name.

Enter 0 if you want to store the empty string.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the specified number of characters.

Yes

String

InputString

Enter the input string from which you want to store the characters.

Yes

String

Length

Specify the number of characters you want to store under the key name. Enter 0 if you want to store an empty string.

Yes

String

Example:

StoreStringFromLeft     "Key"  "John Doe"    "4"    

In this case, this action stores the value of Key as John.

StoreSqRoot

This action stores the square root of the specified number under the key. The stored key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Number

Enter the number whose square root you want to store.

Yes

String

Key

Enter the key name under which you want to store the square root.

Yes

String

 

Example:

StoreSqRoot              "144"             "Key"

In this case, the 12 will be stored under key.

 

Example:

StoreStringFromLeft                      "John Doe"             "4"          "Key"

In this case, the first four characters i.e. Jonn will be stored under the key name.

StoreIntegerSign

This action stores an integer that indicates sign of the number specified in the parameter. The key value can be retrieved using the key name.

  • If number is greater than 0, stores 1.

  • If number is equal to 0, stores 0.

  • If number is lesser than 0, stores -1.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the integer value.

Yes

String

Number

 

Enter the number whose integer value you want to store.

 

Yes

String

 

Example:

StoreIntegerSign                    "Key"             "12"

If you enter a negative integer, in this case, the -1 will be stored under key because the number is lesser than 0.

StoreAbsoluteValue

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

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Integer

Enter the integer whose absolute value you want to store.

Yes

String

Key

Enter the key name under which you want to store the absolute value.

Yes

String

 

Example:

StoreAbsoluteValue                "-3.6"              "Key"

In this case, the 3.6 will be stored under key.

StoreMatchesFromRegExPattern

This action fetches all the matches of a regular expression pattern from an InputString and stores the array of all the matches into the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

RegExPattern

Enter the regular expression pattern.

Yes

String

InputString

Enter the data from which you want to store the element.

Yes

String

Key

Enter the key name under which you want to store the matching element.

Yes

String

Example:

StoreMatchesFromRegExPattern                  "Cust1(\d?)"               "CustKey1 CustKey123Cust321"           "Key"

Array.IsArray

This action verifies whether the specified data is in the array form. If the data is not an array, reports a defect in the execution report.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data which you want to verify.

Yes

String

Example:

Array.IsArray              "ArrayKey"

Array.JoinArrayAndStore

This action joins the substrings from an existing array and stores them into the specified key. By default, these substrings are separated by the caret sign (^). The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data which you want to join.

Yes

String

Key

Enter the key name under which you want to store the joined array.

Yes

String

Example:

Array.JoinArrayAndStore                "ArrayKey"            "Key"

Array.Reverse

This action reverses the existing sequence of data given in an array.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data which you want to modify the sequence of.

Yes

String

Example:
Array.Reverse                     "ArrayKey"

Array.Sort

This action sorts the existing array data in an ascending order.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data which you want to sort in an ascending order.

Yes

String

Example:
Array.Sort               "ArrayKey"

Array.StoreArrayLength

This action stores the length of an existing array into the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data whose length you want to store.

Yes

String

Key

Enter the key name under which you want to store the array length.

Yes

String

Example:

Array.StoreArrayLength       "ArrayKey"               "Key"

Array.StoreElementByIndex

This action stores the element from the specified index of an array into the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data from which you want to store the element.

Yes

String

Index

Enter the index of the element which you want to store.

Yes

String

Key

Enter the key name under which you want to store the element.

Yes

String

Example:
Array.StoreElementByIndex                  "ArrayKey"          "5"           "Key"

Array.StoreElementIndex

This action stores the index of the specified element from an existing array into the specified key. The key value can be retrieved using the key name.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data from which you want to store the element index.

Yes

String

Element

Enter the element which you want to store.

Yes

String

Occurrence

Enter the number of occurrence from the array which you want to store.

Yes

String

CaseSensitive

Enter whether you want to consider case-sensitivity when comparing content. Value for this parameter can be True or False.

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison.

Yes

String

Key

Enter the key name under which you want to store the index of an element.

Yes

String

Example:

Array.StoreElementIndex                    "ArrayKey"           "Sunday"           "1"           "True"         "Key"

Array.VerifyElementExist

This action verifies whether the specified item exists in an array and reports a defect in case of not finding the specified item.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ArrayKey

Enter the key that holds an array data from which you want to verify the element.

Yes

String

Element

Enter the element which you want to verify.

Yes

String

CaseSensitive

Enter whether you want to consider case-sensitivity when comparing content. Value for this parameter can be True or False.

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison.

Yes

String

Example:
Array.VerifyElementExists                        "ArrayKey"             "Sunday"             "True"

LeftTrimAndStore

This action removes or trims the blank spaces existing at the extreme left side of the specified string and stores the value 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 you want to store the final value.

Yes

String

InputString

Enter the string from which you want to trim the blank space.

Yes

String

Example:

LeftTrimAndStore         "Key"      "       John and family"            

In this case, the John and family will be stored under key. The blank space before john will be removed.

RightTrimAndStore

This action removes or trims the blank spaces existing at the extreme right side of the specified string and stores the value 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 you want to store the final value.

Yes

String

InputString

Enter the string from which you want to trim the blank space.

Yes

String

Example:

RightTrimAndStore         "Key"       "John and family           "           

In this case, the John and family will be stored under key. The blank space after john and family will be removed.

IMAGE.CompareTwoImages

This action compares two images. The file extension and resolution of both the images (source and target) should be same, otherwise, the step will fail.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

SourceImagePath

Enter the absolute path to the source image which you want to compare.

Yes

String

TargetImagePath

Enter the absolute path to the target image with which you want to compare the source image.

Yes

String

Example:

IMAGE.CompareTwoImages    “C:\Users\Qualitia\Cust_Sign.png”        “C:\Users\Qualitia\Cust_Logo.png”

Date.StoreModified Date

This action modifies the date interval based on the data provided by the user and stores the modified date in the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Inputdate

Enter the date to which you want to add the interval.

Yes

String

Interval

Enter the interval which you want to modify. Value for this parameter can be as follows:

  • yyyy - Year

  • q - Quarter

  • m - Month

  • y - Day of year

  • d - Day

  • w - Weekday

  • ww - Week of year

  • h - Hours

  • n - Minutes

  • s – Seconds

Yes

String

Data

Enter the number of intervals you want to add to the input date. The number can be positive for future dates and negative for dates in the past.

Yes

String

Key

Enter the key name under which you want to store the modified date. The key value can be retrieved using the key name.

Yes

String

Example:

Data.StoreModifiedDate “02/28/2001”     “yyyy”    “20”    “Key”

Post execution, Qualitia will store 02/28/2021 in the key.

Date.ChangedDateFormat

This action modifies format of the date and time based on the format specified by the user and stores the date and time in the modified format under the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Inputdate

Enter the date whose format you want to change.

Yes

String

Interval

Enter the value for the format you want to update the date into. Value for this parameter can be as follows:

  • 0 – Converts current date into mm/dd/yy and time (if specified) into hh:mm:ss PM/AM.

  • 1 – Converts current date into weekday, monthname, year format.

  • 2 – Converts current date into mm/dd/yy format.

  • 3 – Converts current time into hh:mm:ss PM/AM format

  • 4 - Converts current time into hh:mm format.

Yes

String

Key

Enter the key name under which you want to store the modified date. The key value can be retrieved using the key name.

Yes

String

Example:

Date.ChangeDateFormat           “02/28/2021”     “1”    “Key”

Post execution, Key is stored in the new modified date format to Sunday, February 28, 2021.

Excel.StoreCellData

This action stores the value available in the specified cell. You can then use this data while developing tasks and test cases.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filePath

Enter absolute path to the Excel file from which you want to get and store the value.

Yes

String

sheetname

Enter the sheet name from the Excel file from which value is to be stored.

Yes

String

rowNumber

Enter the row number of the cell from which you want to store the value.

Yes

String

column

Enter the column ID or column name from which you want to store the value in the following format.

  •  

Column ID either can be an index number of the column or column header (mentioned at the top of each column, starts from the letter A). For example: to specify 2nd column, use col::2 or col::B.

  •  

Column name: Enter the name of the column from which you want to store the value. This name is provided by the user while adding data.

Yes

String

Key

Enter the key name under which you want to store the value. The key value can be retrieved using the key name.

Yes

String

 

Example:

EXCEL.StoreCellData               “D:\TrainingStatus.xlsx”           “Sheet1”         “3”      “Col::3”          “Key”

Excel.WriteToRow

This action adds specified value or a set of values into the specified row of the Microsoft excel file.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filePath

Enter absolute path to the Excel file.

Yes

String

sheetname

Enter the sheet name from the Excel file in which you want to add the values.

Yes

String

rowNumber

Enter the row number in which you want to add the value.

Yes

String

column

Enter the column ID or column name in which you want to add the value in the following format.

  •  

Column ID either can be an index number of the column or column header (mentioned at the top of each column, starts from the letter A). For example: to specify 2nd column, use col::2 or col::B.

  •  

Column name: Enter the name of the column from which you want to store the value. This name is provided by the user while adding data.

Yes

String

data

This is the data to be added to the specified Excel row. In case you are statically creating an array, values should be separated by caret (^).

Yes

Array

overWrite

Specify whether you want to overwrite the existing data or you want to add another row to add this data. Values for this parameter can be as follows:

  • Enter Previous to add a new row before the row specified above.

  • Enter Next to add a new row after the row specified above.

  • Enter Current to overwrite new values over the existing set of values.

No

String

 

Example:

EXCEL.WriteToRow                   “D:\TrainingStatus.xlsx”                “Sheet1”            “3”               “Col::3”         “PASS^PASS^FAIL^WIP”              “Current”

Excel.WriteToColumn

This action adds the specified value or a set of values into the specified column of the Microsoft Excel file.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filePath

Enter absolute path to the Excel file.

Yes

String

sheetname

Enter the sheet name from the Excel file in which you want to add the values.

Yes

String

rowNumber

Enter the row number in which you want to add the value.

Yes

String

Column

Enter the column ID or column name in which you want to add the value in the following format.

  •  

Column ID either can be an index number of the column or column header (mentioned at the top of each column, starts from the letter A). For example: To specify the 2nd column, use col::2 or col::B.

  •  

Column Name: Enter the name of the column from which you want to store the value. This name is provided by the user while adding data.

Yes

String

Data

You need to add the data in the specified Excel row. In case you are statically creating an array, values should be separated by caret (^).

Yes

Array

Overwrite

Specify whether you want to overwrite the existing data or you want to add another row to add this data. Values for this parameter can be as follows:

  •  

    • Enter Previous to add a new column before the column specified above.

    • Enter Next to add a new column after the column specified above.

    • Enter Current to overwrite new values over the existing set of values.

No

String

 

Example:

EXCEL.WriteToColumn               “D:\TrainingStatus.xlsx”           “Sheet1”           “3”          “Col::3”         “USER1^ USER2^ USER3^ USER4”          “Previous”

Excel.StoreColumnCount

This action stores the total number of columns present in the specified sheet of Microsoft Excel.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filePath

Enter absolute path to the Excel file.

Yes

String

sheetname

Enter the sheet name from the Excel file from which you want to store the column count.

Yes

String

ignoreBlankColumn

Specify whether you want to ignore the blank columns while calculation.

  • To ignore blank columns, use True.

  • To consider even blank columns, use False.
    Note: The default value is True.

No

Boolean

Key

Enter the key name under which you want to store the value.

Yes

String

Example:

Excel.StoreColumnCount           “D:\TrainingStatus.xlsx”          “Sheet1”         “True”        “Key”

Excel.StoreRowCount

This action stores the total number of rows present in the specified sheet of Microsoft Excel.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the value.

           Yes

String

filePath

Enter the absolute path to the Excel file.

Yes

String

sheetname

Enter the sheet name from the Excel file from which you want to store the row count.

Yes

String

ignoreBlankRows

Specify whether you want to ignore the blank rows while calculation.

  • To ignore blank rows, use True.

  • To consider even blank rows, use False.

No

String

Example:

Excel.StoreRowCount       “Key”    “D:\TrainingStatus.xlsx”       “Sheet1”    “True”

Excel.StoreColumnDataOccurrance

This action stores the occurrence of the specific value into the specified column.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filePath

Enter absolute path to the Excel file.

Yes

String

sheetname

Enter the sheet name from the Excel file in which you want to check for the data.

Yes

String

ColumnNumber

Enter the column ID or column name in which you want to add the value in the following format.

  • Column ID either can be an index number of the column or column header (mentioned at the top of each column, starts from the letter A). For example: to specify 2nd column, use col::2 or col::B

  • Column name: Enter the name of the column from which you want to store the value. This name is provided by the user while adding data.

Yes

String

Data

Enter the data in the specified Excel row. In case you are statically creating an array, values should be separated by caret (^).

Yes

String

Key

Enter the key name under which you want to store the occurrence.

Yes

String

Example:

Excel.StoreColumnDataOccurrance              “D:\TrainingStatus.xlsx”    "Sheet1”   "5"        “True”        “Key”

Excel.StoreCellDataFromFile

This action checks the condition added by the user and stores the matching data from specified Excel cell into the specified key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filename

Enter the absolute path to the excel file from which you want to read and store the data.

Yes

String

sheetName

Enter the name of the sheet from which you want to fetch the data.

Yes

String

colName

Enter the column name from which you want to fetch the data.

Yes

String

Condition

Enter the condition which you want to match for getting the desired data.

Yes

String

Separator

Specify the separator which you have used to separate column name and data while adding the condition. You can use any character as a separator (equal to [=] sign in the example mentioned below). Use caret sign (^) as a connection string. 

Yes

String

strKey

Enter the key in which you want to store the data.

Yes

String

Example:

EXCEL.StoreCellDataFromFile

Suppose there is list of employees and you want to store the employee ID of the specific employee from the list. (refer to the image below). To store the employee ID of Jane, you can use this action as follows:

"D\Book1.xlsx" "Sheet1"                "Employee ID"             "FirstName=Jane^LastName=Doe^Designation=Asst.Manager"          "="          "ID"

End of the execution, action stores the Employee ID of Jane i.e. 232 into the specified key ID.

File.CompareFileContents

This action is used to compare two text files to validate whether their content is same.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

File1

Enter the absolute path to the source file from which you want to compare the content.

Yes

String

File2

Enter the absolute path to the target file with which you want to compare the source file content.

Yes

String

CaseSensitive

Enter whether you want to consider case-sensitivity when comparing content. Value for this parameter can be True or False.

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison.

Yes

String

IgnoreWhitespace

Enter whether you want to consider whitespaces when comparing file contents. Value for this parameter can be True or False.

  • Set True if you want to consider whitespaces.

  • Set False if you want to ignore whitespaces.

Note: Only leading and trailing whitespaces will be ignored if you set this parameter to True. Whitespaces inside the content will not be considered.

Yes

Boolean

Example:

File.CompareFileContents                  “C:\Users\admin\Downloads\Cust_Info.txt”               “C:\Users\admin\Downloads\Client_list.txt”        “False”       “True”

FILE.StoreCharacterCount

This action stores the total number of characters present in the specified text file. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

FilePath

Enter the absolute path to the file from which you want to store characters.

Yes

String

Key

Enter the key name in which you want to store the character count.

Yes

String

IgnoreWhitespace

Enter whether you want to consider whitespaces when storing character count. Value for this parameter can be True or False.

  • Set True if you do not want to consider tabs and spaces as characters.

  • Set False if you want to consider tabs and spaces as characters.

Note: A space or a tab is counted as one character.

Yes

String

Example:

FILE.StoreCharacterCount        “C:\Users\admin\Downloads\Cust_Info.txt”        “Key”       “True”

FILE.StoreStringByLineNumber

This action stores data from the specified row of the specified text file in the key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

FilePath

Enter the absolute path to the file from which you want to store data.

Yes

String

RowNumber

Enter the row number from which you want to get and store the data.

Yes

String

Key

Enter the key name in which you want to store the data.  

Yes

String

Example:

FILE.StoreStringByLineNumber        “C:\Users\admin\Downloads\Cust_Info”     “2”    “Key”

FILE.VerifyStringExistInFile

This action verifies whether the specified data exists in the specified text file.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

FilePath

Enter the absolute path to the file in which you want to verify data.

Yes

String

Data

Enter the data which you want to verify in the file.

Yes

String

CaseSensitive

Enter whether you want to consider case-sensitivity when verifying data. Value for this parameter can be True or False.

  • Set True for case-sensitive comparison.

  • Set False for case-insensitive comparison. 

Yes

String

Example:

FILE.VerifyStringExistInFile       “C:\Users\admin\Downloads\Cust_Info”     “Qualitia”    “True”

File.VerifyFileExist

This action verifies the existence of the specified file at the specified location.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

FilePath

Enter the absolute path to the file which you want to verify.

Yes

String

Example:

File.VerifyFileExist        “C:\Users\admin\Downloads\Cust_List.txt”

File.VerifyFolderExist

This action verifies the existence of the specified folder at the specified location.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

FolderPath

Enter the path to the folder which you want to verify.

Yes

String

Example:

File.VerifyFolderExist        “C:\Users\admin\Downloads\Cust_Info”

IsArraySorted

This action verifies whether the array is sorted in ascending/descending order.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

array data

The array to be verified for ascending or descending order.
The list of data provided should be carat(^) separated.

Yes

Array

datatype

This is the type of data considered for testing. Supported data types are
STRING : These are combination of alphanumeric and special characters items. 
INTEGER : These are strictly numerical items.

Yes

String-

direction

The way the data are to be sorted, i.e. in either ascending or descending. Supported directions are:
1=indicates ascending
2=indicates descending

Yes

String

Example:
IsArraySorted                  "0^1^4^10"               "Integer"             "1"

PDF.VerifyStringExistInPDF

This action searches specified text in the PDF file.

Prerequisite:

Before executing this action, ensure you:

  1. Download XPDF Tools and

  2. Add XPDF tools directory to system path environment variables.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

pdfFile

Enter the absolute path to the PDF file in which you want to find the text.

Yes

String

textToFind

Enter the text you want to find in the specified PDF file.

Yes

String

Example:

PDF.VerifyStringExistInPDF   “C:\Users\Qualitia\Cust_List.pdf”      “Qualitia”

PDF.VerifyStringExistInPDFPage

This action searches specified text on the specified page of the PDF file.

Prerequisite:

Before executing this action, ensure you:

  1. Download XPDF Tools and

  2. Add XPDF tools directory to system path environment variables.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

pdfFile

Enter the absolute path to the PDF file in which you want to find the text.

Yes

String

textToFind

Enter the text you want to find in the specified PDF file.

Yes

String

pageNumber

Enter the page number on which you want to search the specified text.

Yes

String

Example:

PDF.VerifyStringExistInPDFPage   “C:\Users\Qualitia\Cust_List.pdf”      “Qualitia”       “2”

PDF.ComparePDF

This action compares two PDFs and validates whether content inside them is identical and stores differences in the temporary text file.

Prerequisite:

Before executing this action, ensure you:

  1. Download XPDF Tools and

  2. Download and install GnuWin

  3. Add XPDF Tools and GnuWin installation directory to system path environment variables.
    For example: D:\XPDF\xpdf-tools-win-4.00;C:\Program Files (x86)\GnuWin32\bin

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Pdf1

Enter the absolute path to the PDF file which you want to compare.

Yes

String

Pdf2

Enter the absolute path to the PDF file with which you want to compare the source file.

Yes

String

diffFilePath

Enter the absolute path to the text file in which you want to store the PDF comparison results.

Yes

String

Example:

PDF.ComparePDF   “C:\Users\Qualitia\Cust_List.pdf”      “C:\Users\Qualitia\Client_List.pdf”    “C:\Users\Qualitia\Diff.txt”

StoreClipboardData

This action stores the data present on the clipboard into the specified key. The key value then can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the data. The key value then can be retrieved using the key name.

Yes

String

Example:

StoreClipboardData                 "key"

StoreFixNumber

This action stores the integer part of a specified number into the specified key. The stored key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name in which you want to store the updated string.

Yes

String

Number

Enter the number from which you want to store the integer part.

Yes

String

 

Example:

StoreFixNumber           "Key"              "6.4332"

WaitForNumberofWindowsToBe

This action waits until the number of open windows reaches the count specified in the parameter. You may use polling interval and timeout, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumber

Enter expected number of windows.   

No

String

timeOut

Enter the timeout (in seconds) to wait. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check whether the specified count has reached. 

No

String

keyNumOfWindows

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfWindowsToBe       "3"         "10"      "500"       "Key"     "Defect"

WaitForJavaScriptReturnsValue

This action runs the parameterized JavaScript code until it returns the value. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

JavaScriptString

Enter the JavaScript code to run. 

No

String

keyReturnValue

Enter the key under which the javascript return value will be stored. The key value can be retrieved using the key name. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the value. 

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForJavaScriptReturnsValue       "return eval('2-1');"    "key"      "10"      "500"       "Key"     "Defect"  

WaitForJavaScriptThrowsNoExceptions

This action runs the parameterized JavaScript code until it throws the execption. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

JavaScriptString

Enter the JavaScript code to run. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the exception. 

No

String

pollingInterval

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

No

String

keyJSThrowsExceptionStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForJavaScriptThrowsNoExceptions       ""          "10"      "500"       "Key"     "Defect"  

WaitForTitleContains

This action waits for the web page title to contain expected partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Input Parameters: 

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected partial value of the web page title.

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleContains

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleContains      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForTitleNotContains

This action waits until the web page title changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected partial value which should not be in the web page title. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleNotContains      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForTitleToBe

This action waits for the web page title to contain exact expected parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters: 

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected exact value of the web page title.

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleToBe      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForTitleNotToBe

This action waits until the web page title changes to other than the parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

title

Enter the expected exact value which should not be in the web page title. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyTitleNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForTitleNotToBe      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForURLContains

This action waits for the web page URL to contain expected partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the expected partial value of the web page URL. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyURLContains

Enter the key name under which the status of this step will be stored. 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:

WaitForURLContains      "OAuth%9"          "5"          "500"        "Key"        "Defect"

WaitForURLNotContains

This action waits until the web page URL changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the expected partial value which should not be in the web page URL. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyURLNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForURLNotContains      "OAuth%9"          "5"          "500"        "Key"        "Defect"

WaitForURLToBe

This action waits for the web page URL to contain exact expected parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the expected the web page URL. 

No

String

timeOut

Enter the timeout (in seconds) to wait for the expected URL. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected URL before exhausting timeout. 

No

String

keyURLToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForURLToBe      "https://google.co.in"          "5"          "500"        "Key"        "Defect"

WaitForURLNotToBe

This action waits until the specified web page URL value changes to other than the parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

url

Enter the URL which should not be the web page URL.

No

String

timeOut

Enter the timeout (in seconds) to wait for the URL to change. 

No

String

pollingInterval

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

No

String

keyURLNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForURLNotToBe      "https://google.co.in"          "5"          "500"        "Key"        "Defect"

WaitForURLPattern

This action waits until the specified web page URL value changes to the parameterized regular expression pattern. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

urlRegx

Enter the expected pattern for the URL. Pattern should be regular expression. Step fails in case the pattern is invalid.

No

String

timeOut

Enter the timeout (in seconds) to wait for the URL to change. 

No

String

pollingInterval

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

No

String

keyURLPattern 

Enter the key name under which the status of this step will be stored. 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:

WaitForURLPattern      "http[s]:\/\/www\.mysite\.com.*"          "5"          "500"        "Key"        "Defect"

WaitForAlertAndSendText

This action waits for the page to prompt an alert. After the alert is prompted, you can send the text specified in the parameter. You may specify the timeout and polling interval, if required.

After adding the required text, you can use the AcceptDialog or WaitForAlertAndSpecifyBehavior to continue test case execution on the main window.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

textToSend

Enter the text you want to send in the alert. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the alert. 

No

String

pollingInterval

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

No

String

keyAlertAvailable

Enter the key name under which the status of this step will be stored. 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:

WaitForAlertAndSendText      "Qualitia"          "5"          "500"        "Key"        "Defect"

WaitForAlertAndSpecifyBehavior

This action waits for the web page to prompt an alert. After the alert is prompted, you can either accept the dialog or dismiss the dialog giving appropriate values in the parameters. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

acceptOrDismiss

Values for this parameter can be: accept or dismiss.

  • Set accept if you want to accept the dialog. 

  • Set dismiss if you want to dismiss the dialog.  

No

String

timeOut

Enter the timeout (in seconds) to wait for an alert. 

No

String

pollingInterval

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

No

String

keyAlertAvailable

Enter the key name under which the status of this step will be stored. 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:

WaitForAlertAndSpecifyBehavior      "accept"          "5"          "500"        "Key"        "Defect"

WaitForPageToLoad (Deprecated)

This actions waits for the page to load for the specified number of seconds. If the wait time is "" then the wait time value is taken from the "Sync Time" set under the Qualitia Configuration (Execution) window. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTime

Enter the number of seconds to wait.

No

String

Example:
WaitForPageToLoad                        "10"

In Webdriver, we wait for the object to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver will stop waiting. The condition to wait till the object is in ready state and assume that the page is loaded could however not work as expected at all times.

WaitforAlertAndStoreAcceptIfexist

This action waits for the page to prompt an alert. After the alert is prompted, it stores the alert text in the variable. You may specify the timeout if required. After storing the required text, It clicks the OK button on the alert/prompt/confirmation pop up.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 

 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Seconds to wait for an alert to display on the screen..

No

String

Key

Key name under which the alert message will be stored.

No

String

Example:

WaitforAlertandStoreAcceptIfexist     “10“     “AlertMessage”

WriteToTextFile

This action allows users to write or append the text in the specified file.

User performing this action should have write access to the corresponding file and folder.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

FilePath

Enter the absolute path to the file in which you want to make changes.

Yes

String

Text

Enter the content to be overwritten or appended.

Yes

String

Mode

Value of this parameter can be OVERWRITE or APPEND. If user keeps mode empty, it will be considered as append.

Yes

String

Example:
WriteToTextFile                  "C:\Users\Notepad.txt"          "Qualitia"            "A

WebButton Actions

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseDown

This action simulates left-click at the specified location on the screen.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example:
MouseDown                 "5"           "10"

MouseUp

This action simulates the event that occurs when the user releases the mouse button.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

DragAndDropToOffset 

This action drags and drops the specified web element at the specified location.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

No

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

No

String

Example:

DragAndDropOffset            "100"              "500"

VerifyEnability

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

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is existence. 
  • Set False if you want to verify that the object is non-existence.
    Note: If you do not enter any value, the default value is set to True during the test case execution.

Yes

String

Example:

VerifyExistence                          "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is visibility. 
  • Set False if you want to verify that the object is invisibility.
    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"

ClickAt

This action clicks at the specified point on the object.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

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"

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files.  You need to handle the action externally as it does not wait until the file is downloaded.

 Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating system only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist

Yes

String

Filename

The filename of the downloadable file, to be given incase the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. Incase, the user does not provide this data, the action will pick the default file name available while download.

No

String


Example:



Example 

DownloadFile               "C:/ProgramData"           "Qualitia" 

StorePropertyValue

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

Input Parameters:

ParameterName

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key.

Yes

 String

Example:

StorePropertyValue                            "key"                     "text"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:
StoreChildCount                               "Key"

ClickJS

This action clicks the specified object from the web application under test.
This action does not have any parameter.
Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.
Example:
ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'False' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

ClickAction

This action clicks the specified object from the web application under test.
This action does not have any parameter.
Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.
Example:
ClickAction

DoubleClick

This action double-clicks the specified web element.

Example:

DoubleClick

RightClick

This action right-clicks the specified web element.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''
This will select the third option from the context-menu.


SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:
StoreCSSProperty     "Key"     "display"            

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:
StoreLocation        "Height"            "Width"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:
StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:
StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:
SetValueAttribute           "#ff0990"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotContains      "name"           "h"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

This action waits for the specified object to be clickable. 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 be clickable.   

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. 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 existence of the object.   

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. 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 become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. 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 non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.
 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:
WaitForStaleness        "5"          "500"     "Key"       "Defect"

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. 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     "5"          "500"     "Key"       "Defect"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.


StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.No

String

Example: StoreVisibility   "Key"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window. Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continue to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait
Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

ClickandchooseOkOnNextConfirmation (Deprecated)

This action handles the alert or confirmation that comes up post clicking the OK button. This action fails if the button is clicked and no alert or confirmation comes up.

This action does not have any parameter.

Example:

ClickandchooseOkOnNextConfirmation

WebCheckBox Actions

WebEdit Actions

ClearText

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

This action does not have any parameter.

Example:
ClearText

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:
ClickAction

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:
ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DragAndDropToOffset 

This action drags and drops the specified web element at the specified location.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

No

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

No

String

Example:

DragAndDropOffset            "100"              "500"

MouseDown

This action simulates left-click at the specified location on the screen.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example:
MouseDown                 "5"           "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseOverJs

This action simulates a mouse hovering over the specified object by using JavaScript.

This action does not have any parameter. 

Example:

MouseOverJs

MouseUp

This action simulates the event that occurs when the user releases the mouse button.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

RightClick

This action right-clicks the specified web element.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:RightClick             "3''
This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SecureSet

This action enters the expected value into the specified edit box. The value set in the parameter is encrypted once the focus is moved for security purposes.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Text

Enter the test that needs to be entered in the specified text box in the specified format.
Format: Encrypt(<TEXT TO BE ADDED>)

Yes

String

Example:

SecureSet    "Encrypt(Abc)"When the focus is moved away from the parameter Qualitia will automatically encrypt the data ABC and result in a secured text like "vHpmlfI4R3PQkCN4sZnuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

Set

This action enters the specified value into the edit box.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Value

Enter the value that needs to be added into the specified edit box. You can give the alphanumeric value to be entered into the edit box. 

No

String

Example: Set                            "Qualitia"

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 
Example:

SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:
SetValueAttribute           "#ff0990"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:
StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:
StoreCSSProperty      "Key"     "display"  

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:
StoreLocation        "Height"            "Width"

StorePropertyValue

This action stores the property of the specified object under the key name. The stored key value can be retrieved using the key name.
Some Android and iOS properties are not accessible.
List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"
List of accessible properties for iOS: "name", "value", "label", "hint"
Input Parameters:

ParameterName

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example:

StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:
StoreSize           "Height"                   "Width"

StoreText

This action stores the text entered in an edit box 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 under which you want to store the text.

Yes

String

Example:

StoreText                   "textKey"

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

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

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.
    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"

VerifyVisibility

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

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.No

String

Example: StoreVisibility   "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:
WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

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. 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     "5"          "500"     "Key"       "Defect"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 
Example:

ClickAndWait
Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebElement Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:

ClickAction

ClickAt

This action clicks at the specified point on the object.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:
ClickJS

ClickandWait

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.  

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameters.

Example:

DoubleClick

DownloadFile

This action clicks the link or element that opens a download window, which is used to download the files.  You need to handle the action externally as it does not wait until the file is downloaded.

 Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating system only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validate whether the folder exists.

Yes

String

Filename

The filename of the downloadable file, to be given in case the user requires to give a specific name and not depend on the default name of the file. In case, the file already exists, similar window like below will appear. Such windows are not handled by the action. In case, the user does not provide this data, the action will pick the default file name available while downloading.

No

String


Example:



Example  DownloadFile               "C:/ProgramData"           "Qualitia" 


DragAndDropToOffset 

This action drags and drops the specified web element at the specified location.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

Yes

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

Yes

String

Example:

DragAndDropOffset            "100"              "500"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:
MouseOver

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example: RightClick             "3''
This will select the third option from the context-menu.

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:
StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

property

Enter the property name whose value you want to store.YesString

Example:
StoreCSSProperty         "Key"     "display"    

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:
StoreLocation        "Height"            "Width"

StorePropertyValue

This action stores the property of the specified object under the key name. The stored key value can be retrieved using the key name.
Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example: StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyHeight

Enter the key name under which you want to store the height of the object.

Yes

String

keyWidth

Enter the key name under which you want to store the width of the object.

Yes

String

Example:
StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:
StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.
    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"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

strKey

strKey

Enter a variable to store the visibility status.Yes

String

Example: StoreVisibility   "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

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

No

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

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

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

Example:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeValueNotContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:
WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

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. 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     "5"          "500"     "Key"       "Defect"

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "True"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebFile Actions

AttachFile

This action sets a file path in the file object type in html. This action is applicable for uploading a file on a desktop web application only.

The file element that is used to attach your file must have attribute type="file".


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

filePath

Enter the absolute or relative path of the file. 

Yes

String

Example: AttachFile  "c:/Folder/test.txt"

If you want to upload a file without an object, refer to AttachFile action as described in General Web Actions.

Click

This action clicks the specified object.

This action does not have any parameter.
Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.
Example:

ClickAction

ClickAt

This action clicks at the specified point on the object.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files.

You need to handle the action externally as it does not wait until the file is downloaded.

Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist

Yes

String

Filename

The filename of the downloadable file, to be given in case the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. In case, the user does not provide this data, the action will pick the default file name available while download.

No

String


Example:



Example 

DownloadFile               "C:/ProgramData"           "Qualitia" 

DragAndDropToOffset

This action drags and drops the specified web element at the specified location. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

No

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

No

String

Example:

DragAndDropOffset            "100"              "500"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example:

MouseDown                 "5"           "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseUp

This action simulates the event that occurs when the user releases the mouse button.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example MouseUp         "5"          "10"

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 
Example: SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:
SetValueAttribute           "#ff0990"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:
StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 
Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

property


Enter the property name whose value you want to store.YesString

Example:
StoreCSSProperty     "display"      "Key"        

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:
StoreLocation        "Height"            "Width"

StorePropertyValue

This action stores the property of the specified object under the key name. The stored key value can be retrieved using the key name.
Some Android and iOS properties are not accessible.
List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"
List of accessible properties for iOS: "name", "value", "label", "hint"
Input Parameters:

ParameterName

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example: StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyHeight

Enter the key name under which you want to store the height of the object.

Yes

String

keyWidth

Enter the key name under which you want to store the width of the object.

Yes

String

Example:
StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:
StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

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

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.
    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"

VerifyVisibility

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

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.Yes

String

Example: StoreVisibility   "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

  
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

Integer

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

Integer

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:
WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait
Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebFrame Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:
ClickAction

ClickAt

This action clicks at the specified point on the object.
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.
Example:
ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 

  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

No

String

isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.

  • False: If you do not want to apply the regex pattern to URL.

No

String

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.


DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseOverJs

This action simulates a mouse hovering over the specified object by using JavaScript.

This action does not have any parameter. 

Example:

MouseOverJs

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

StoreText

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SelectFrame

This action selects the frame within the current window.

Example:

SelectFrame 

SelectFrameWhenAvailable

This action waits until the specified frame appears on the page and selects when the frame appears. You may specify the timeout and polling interval if required. 

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the frame to appear.  

No

String

pollingInterval

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

No

String

keyFrameAvailable

Enter the key name under which the status of this step will be stored. 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:

SelectFrameWhenAvailable        "20"             "500"          "Key"          "Defect"

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 


Input Parameters:


Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array


Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.


Key

Syntax

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

UP

~{UP~}

TAB

~{TAB~}

SUBTRACT

~{SUNSTRACT~}

SPACE

~{SPACE~}

SHIFT

~{SHIFT~}

SEPARATOR

~{SEPARATOR~}

SEMICOLON

~{SEMICOLON~}

RIGHTCLICK

~{CONTEXTCLICK~}

RIGHT

~{RIGHT~}

RETURN

~{RETURN~}

PAUSE

~{PAUSE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

NUMPAD9

~{NUMPAD9~}

NUMPAD8

~{NUMPAD8~}

NUMPAD7

~{NUMPAD7~}

NUMPAD6

~{NUMPAD6~}

NUMPAD5

~{NUMPAD5~}

NUMPAD4

~{NUMPAD4~}

NUMPAD3

~{NUMPAD3~}

NUMPAD2

~{NUMPAD2~}

NUMPAD1

~{NUMPAD1~}

NUMPAD0

~{NUMPAD0~}

NULL

~{NULL~}

MULTIPLY

~{MULTIPLY~}

META

~{META~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

LEFT_ALT

~{LEFT_ALT~}

LEFT

~{LEFT~}

INSERT

~{INSERT~}

HOME

~{HOME~}

HELP

~{HELP~}

F12

~{F12~}

F11

~{F11~}

F10

~{F10~}

F9

~{F9~}

F8

~{F8~}

F7

~{F7~}

F6

~{F6~}

F5

~{F5~}

F4

~{F4~}

F3

~{F3~}

F2

~{F2~}

F1

~{F1~}

ESCAPE

~{ESCAPE~}

EQUALS

~{EQUALS~}

ENTER

~{ENTER~}

END

~{END~}

DOWN

~{DOWN~}

DOUBLECLICK

~{DOUBLECLICK~}

DIVIDE

~{DIVIDE~}

DELETE

~{DELETE~}

DECIMAL

~{DECIMAL~}

CONTROL

~{CONTROL~}

COMMAND (META)

~{COMMAND~}

CLICK

~{CLICK~}

CLEAR

~{CLEAR~}

CANCEL (Esc)

~{CANCEL~}

BACK_SPACE

~{BACK_SPACE~}

ARROW_UP

~{ARROW_UP~}

ARROW_RIGHT

~{ARROW_RIGHT~}

ARROW_LEFT

~{ARROW_LEFT~}

ARROW_DOWN

~{ARROW_DOWN~}

ALT

~{ALT~}

ADD

~{ADD~}


SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:

SetValueAttribute           "#ff0990"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:

StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

property


Enter the property name whose value you want to store.

Yes

String

Example:

StoreCSSProperty     "display"      "Key"        

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String


Example:

StoreLocation        "Height"            "Width"

StorePropertyValue

This action stores the property of the specified object under the key name. The stored key value can be retrieved using the key name.
Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example:

StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:

StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:

StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.


Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String


Example:
StoreValueAttribute        "Key"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 

  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.

  • Set False if you want to check the non-existence.
    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"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.

  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.

  • False: If the web element is not visible.


Input Parameters:


Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.

No

String


Example: StoreVisibility   "Key"

Wait Actions

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

This action waits for the specified object to be clickable. 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 be clickable.   

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. 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 existence of the object.   

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. 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 become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. 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 non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

Integer

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

Integer

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForStaleness        "5"          "500"     "Key"       "Defect"

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. 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     "5"          "500"     "Key"       "Defect"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Input Parameters:


Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.

  • Set False if you want to check for the disappearance of the object.

No

String


Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebImage Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:
ClickAction

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files. You need to handle the action externally as it does not wait until the file is downloaded.

Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist

Yes

String

FileName

The filename of the downloadable file, to be given incase the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. Incase, the user does not provide this data, the action will pick the default file name available while download.

No

String


Example:



Example  DownloadFile               "C:/ProgramData"           "Qualitia" 


DragAndDropToOffset 

This action drags and drops the specified web element at the specified location.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

No

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

No

String

Example:

DragAndDropOffset            "100"              "500"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String


Example:

MouseDown                 "5"           "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseOverJs

This action simulates a mouse hovering over the specified object by using JavaScript.

This action does not have any parameter. 

Example:

MouseOverJs

RightClick

This action right-clicks the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example

RightClick       "3"

Note: This will select the third option from the context menu.

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 


Input Parameters:

Parameter Name
Parameter Description
Mandatory
Data Type
arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

YesArray

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

UP

~{UP~}

TAB

~{TAB~}

SUBTRACT

~{SUNSTRACT~}

SPACE

~{SPACE~}

SHIFT

~{SHIFT~}

SEPARATOR

~{SEPARATOR~}

SEMICOLON

~{SEMICOLON~}

RIGHTCLICK

~{CONTEXTCLICK~}

RIGHT

~{RIGHT~}

RETURN

~{RETURN~}

PAUSE

~{PAUSE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

NUMPAD9

~{NUMPAD9~}

NUMPAD8

~{NUMPAD8~}

NUMPAD7

~{NUMPAD7~}

NUMPAD6

~{NUMPAD6~}

NUMPAD5

~{NUMPAD5~}

NUMPAD4

~{NUMPAD4~}

NUMPAD3

~{NUMPAD3~}

NUMPAD2

~{NUMPAD2~}

NUMPAD1

~{NUMPAD1~}

NUMPAD0

~{NUMPAD0~}

NULL

~{NULL~}

MULTIPLY

~{MULTIPLY~}

META

~{META~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

LEFT_ALT

~{LEFT_ALT~}

LEFT

~{LEFT~}

INSERT

~{INSERT~}

HOME

~{HOME~}

HELP

~{HELP~}

F12

~{F12~}

F11

~{F11~}

F10

~{F10~}

F9

~{F9~}

F8

~{F8~}

F7

~{F7~}

F6

~{F6~}

F5

~{F5~}

F4

~{F4~}

F3

~{F3~}

F2

~{F2~}

F1

~{F1~}

ESCAPE

~{ESCAPE~}

EQUALS

~{EQUALS~}

ENTER

~{ENTER~}

END

~{END~}

DOWN

~{DOWN~}

DOUBLECLICK

~{DOUBLECLICK~}

DIVIDE

~{DIVIDE~}

DELETE

~{DELETE~}

DECIMAL

~{DECIMAL~}

CONTROL

~{CONTROL~}

COMMAND (META)

~{COMMAND~}

CLICK

~{CLICK~}

CLEAR

~{CLEAR~}

CANCEL (Esc)

~{CANCEL~}

BACK_SPACE

~{BACK_SPACE~}

ARROW_UP

~{ARROW_UP~}

ARROW_RIGHT

~{ARROW_RIGHT~}

ARROW_LEFT

~{ARROW_LEFT~}

ARROW_DOWN

~{ARROW_DOWN~}

ALT

~{ALT~}

ADD

~{ADD~}

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:

SetValueAttribute           "#ff0990"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:

StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:

StoreCSSProperty    "Key"     "display"            

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:

StoreLocation        "Height"            "Width"

StorePropertyValue

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

Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example:

StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:
StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:

StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.

No

String

Example:

VerifyExistence                      "True"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.No

String

Example: StoreVisibility   "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

Integer

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

Integer

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

ClickAndWait Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebLink Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAndWait

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

ClickandchooseOkOnNextConfirmation (Deprecated)

This action handles the alert or confirmation that comes up post clicking the OK button. This action fails if the button is clicked and no alert or confirmation comes up.

This action does not have any parameter.

Example:

ClickandchooseOkOnNextConfirmation

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:

ClickAction

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickIfExists

This action clicks the object if the specified object exists.

This action does not have any parameters.

Example

ClickIfExists

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files. You need to handle the action externally as it does not wait until the file is downloaded.

Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist

Yes

String

Filename

The filename of the downloadable file, to be given incase the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. Incase, the user does not provide this data, the action will pick the default file name available while download.

No

String


Example:



Example 

DownloadFile               "C:/ProgramData"           "Qualitia" 


DragAndDropToOffset 

This action drags and drops the specified web element at the specified location.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

Yes

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

Yes

String

Example:

DragAndDropOffset            "100"              "500"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseOverJs

This action simulates a mouse hovering over the specified object by using JavaScript.

This action does not have any parameter. 

Example:

MouseOverJs

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The x-coordinate of the click.

No

String

Example:

MouseDown                 "5"           "10"

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example: SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:

SetValueAttribute           "#ff0990"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:
StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:
StoreCSSProperty     "Key"       "display"

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:
StoreLocation        "Height"            "Width"

StorePropertyValue

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

Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example: StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object in terms of height and width. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyHeight

Enter the key name under which you want to store the height of the object.

Yes

String

keyWidth

Enter the key name under which you want to store the width of the object.

Yes

String

Example:

StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String


Example:

StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.

No

String

Example:

VerifyExistence                      "True"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

ClickandChooseOkOnNextConfirmation (Deprecated)

This action handles the alert or confirmation that comes up post clicking the OK button. This action fails if the button is clicked and no alert or confirmation comes up.

This action does not have any parameter.

Example:

ClickandChooseOkOnNextConfirmation

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.No

String

Example: StoreVisibility   "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

Integer

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

Integer

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

ClickAndWait Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebList Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:

ClickAction

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:
ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

DeselectAll

This action deselects all the options from the web list. 

This action does not have any parameter.  

Example:

DeselectAll

DeselectItemByText

This action deselects option specified in the parameter.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

itemName

Enter the item name you want to deselect. 

Yes

String


Example:

DeselectItemByText           "Name"

DeselectItemByValue

This action deselects the specified parameterized item from the list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the item that you want to deselect from the list.

Yes

String

Example:

DeselectItemByValue            "Name"

DeSelectItems

This action deselects the specified selected items from the specified list box. Multiple items for deselection can be given only for the list box that has multi-selection property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the expected list items that are to be deselected from the list box. Separate multiple items by carat (^) operator.

No

Array

Example:

Consider a list containing names of countries. If it contains list items in the order "India", "England", "Australia" , "SA" , if the user wishes to deselect "India and Australia", then this action can be used as follows:

DeSelectItems                                 "India^Australia"

 If an empty data ("" or $NULL$) is passed as the data, the action will passed only if there exist an "" item in the webList to be deselected.

DeselectMultipleItemsByIndex

This action deselects multiple items specified in the parameter. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

indices

Enter the indices of the items you want to deselect. Multiple items should be separated by (^) caret. Index starts from 1.

Yes

Array


Example:

DeselectMultipleItemsByIndex      "1^5^8"

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files. You need to handle the action externally as it does not wait until the file is downloaded.

Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the Auto Install Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist

Yes

String

Filename

The filename of the downloadable file, to be given incase the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. Incase, the user does not provide this data, the action will pick the default file name available while download.

No

String


Example:



Example 

DownloadFile               "C:/ProgramData"           "Qualitia" 

DragAndDropToOffset 

This action drags and drops the specified web element at the specified location.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

No

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

No

String

Example:

DragAndDropOffset            "100"              "500"

IsMultiselectList

This action verifies that web list element supports selecting multiple options and stores the result under the specified key

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the result will be stored. The key value can be retrieved using the key name.

  • Stores True if the web list can select multiple options. 
  • Stores False if the web list cannot select multiple options. 

No

String

Example:

IsMultiselectList          "Key"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The x-coordinate of the click.

No

String

Example:

MouseDown                 "5"           "10"

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SelectItemAndWait (Deprecated)

This action selects an item from the list and waits. It waits for the sync time set under the Configuration Settings (Execution) window. If the page loads before reaching the maximum sync time, then the action will stop waiting.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

item

Enter the item to be selected from the list.

No

String

Example:

Consider a list containing names of countries. If it contains list items "India", "England", "Australia" and the user wishes to select "England", then this action can be used as follows

SelectItemAndWait                      "India"

If an empty data ("" or $NULL$) is passed as the data, the action will passed only if there exist an "" item in the webList.Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document is in ready state and assume that the page is loaded could however not work as expected at all times.

SelectItemByIndex

This action selects the specified item from the list. Index starts from 1. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

index

Enter the index value of the list item that you want to select. Index starts at 1.

No

String


Example:

Consider a list containing names of countries. If it contains list items in the order "India", "England", "Australia" and user wishes to select "Australia", then this action can be used as follows:

SelectItemByIndex                         "3"

SelectItemByText

This action selects option specified in the parameter.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

itemName

Enter the item name you want to select. 

Yes

String


Example:

SelectItemByText           "Name"

SelectItemByValue

This action selects the item specified by value from the web list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Value

Enter the value of the item which you want to select. 

Yes

String


Example:

SelectItemByValue           "Address 1"

SelectItems

This action selects particular item or items from a list. Multiple items for selection can be given only for the list box that has multi-selection property.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the name of the item that needs to be selected.You can  have multiple items by using carat (^) operator to separate them.

No

Array


Example:

SelectItems                                         "England^India^Australia"

Consider a list containing names of countries. If it contains list items "India", "England", "Australia" and the user wishes to select "England", then this action can be used as follows. If an empty data ("" or $NULL$) is passed as the data, the action will be passed only if there exist an item "" in the webList to be selected.

SelectMultipleItemsByIndex

This action selects multiple items specified in the parameter. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

indices

Enter the indices of the items you want to select. Multiple items should be separated by (^) caret. Index starts from 1.

Yes

Array


Example:

SelectMultipleItemsByIndex                "1^2^4"

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 
Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String


Example:

SetValueAttribute           "#ff0990"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String


Example:

StoreChildCount                               "Key"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:

StoreCSSProperty         "Key"    "display" 

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"

StoreFirstSelectedItem

This action stores the first item 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 you want to store the item name. 

Yes

String


Example:

StoreFirstSelectedItem          "Key"

StoreItems

This action stores all the items from the specified list under the key name. Items are separated by carat (^) operator and can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store the items. 

Yes

String


Example:

Consider a list having the items like, Monday, Tuesday, Wednesday.

StoreItems                       "Key"

The items in the key will be stored as Monday^Tuesday^Wednesday.

StoreItemCount

This action stores the total number of elements existing in the specified web list object.

Input parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which the value will be stored. The value can be retrieved using the key name.

Yes

String

Example:

StoreItemCount          "Key"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:

StoreLocation        "Height"            "Width"

StorePropertyValue

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

Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String


Example:

StorePropertyValue                            "key"                     "text"

StoreSelectedItems

This action stores all the items of a list that are selected under the specified key. Multiple items are stored separated by carat (^) operator. 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 you want to store the items. 

Yes

String

Example:
StoreSelectedItems                  "selectedItemsKey"

Consider a list having the items Monday, Tuesday, Wednesday, Thursday, Friday. Suppose Tuesday and Friday is selected in the list.

The items in the key will be stored as Tuesday^Friday

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:

StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Desciption

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:
StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.
No

String

Example:

VerifyExistence                      "True"

VerifyItemsExist

This action verifies the existence of the objects in the specified list. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the items for which you want too check the existence. Separate multiple items by carat (^) operator. 

Yes

Array

existence

Value of this parameter can be either True or False.

  • Set True if you want to check the object existence.
  • Set False if you want to check the object non-existence. 

Yes

String

Example:

Consider a list containing names of countries "India", "Australia", "England", "South Africa". If the user wishes to verify if India, England, South Africa are in the list, then this action can be used as follows:

VerifyItemsExist            "India^South Africa^England"           "True"

  1. "^" in Qualitia is a delimiter for items in an array.
  2. If an empty data ("" or $NULL$) is passed as the data, the action will passed only if there exist an "" item in the webList.

VerifyItemsInSequence

This action verifies whether the sequence of items in the specified web list is correct.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the list of items in expected sequence. Separate multiple items by carat (^) operator. 

No

Array

Example:

Consider a list containing names of countries. If it contains list items in the order "India", "England", "Australia" , "SA" then to verify a sequence in the list, this action can be used as follows:

VerifyItemsInSequence                "India^England^Australia^SA"

VerifyNoItemsDuplication

This action verifies that the specified list does not contain duplicate items.

Example:

VerifyNoItemsDulication

Consider a list having the items Monday, Tuesday, Wednesday, Monday

In this case, this action fails because the list contains Monday two times.

VerifySelectedItems

This action verifies the selected items with the expected items list.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

items

Enter the list items that are expected to be selected from the list box. Separate multiple items by carat (^) operator.

No

Array

Example:

Consider a list containing names of countries. If it contains list items in the order "India", "England", "Australia" , "SA" , if India and England are selected and this needs to be verified, the this action can be used as follows

VerifySelectedItems                                       "India^England"

If an empty data ("" or $NULL$) is passed as the data, the action will passed only if there exist an "" selected item in the webList.

VerifySize

This action compares the actual number of items (size) from the specified list box with the expected number of items (size).

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedSize

Enter the expected size of the list box that will be compared with the actual size of the list box.
The data type of this parameter is Numeric.

No

String

Example:

If a list contains the items "India","England,"S.A", then to verify its size this action can be used as follows.

VerifySize                         "3"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.No

String

Example: StoreVisibility   "Key"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"Example:

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForSelection

This action waits till the specified object gets selected. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keySelection

Enter the key name under which the status of this step will be stored. 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. Default value is Fail. You can override this with Defect.

No

String

Example:

WaitForSelection      "5"          "500"     "Key"       "Defect"

WaitForSelectionStateToBe

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedSelectionState

Enter the expected selection state. Set True for selection and False for deselection.

No

Boolean

timeOut

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

No

String

pollingInterval

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

No

String

keySelectionState

Enter the key name under which the status of this step will be stored. 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. Default value is Fail. You can override this with Defect.

No

String

Example:

WaitForSelectionStateToBe          "False"        "5"          "500"       "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, the execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

WebPage Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:

ClickAction

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String


Example

ClickAt        "5"            "10"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

ClickLinkByText

This action clicks the link specified by the user on the page.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

link

Enter the text of the link which you want to click. 

Yes

String

Example:

ClickLinkByText                             "Advanced Search"

DoubleClickLinkByText

This action double-clicks the link specified by the user on the page.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

link

Enter the text of the link which you want to double-click. 

Yes

String

Example

DoubleClickLinkByText           "Advanced Search"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example:

MouseDown                 "5"           "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseOverJs

This action simulates a mouse hovering over the specified object by using JavaScript.

This action does not have any parameter. 

Example:

MouseOverJs

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString


Example:

StoreCSSProperty     "Key" "display"            

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"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:

StoreLocation        "Height"            "Width"

StorePropertyValue

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

Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example:

StorePropertyValue                            "key"                     "text"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:

StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:

StoreText        "Key" 

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Value for this parameter can be true or false.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.

No

String

Example:

VerifyExistence                      "True"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be true or false.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:
WaitForStaleness        "5"          "500"     "Key"       "Defect"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.
No

String

Example: StoreVisibility   "Key"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

WebRadioButton Actions

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

existence

Value for this parameter can be True or false.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.

No

String

Example: VerifyExistence                      "True"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or false.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the visibility status.
No

String

Example: StoreVisibility   "Key"

Click

This action clicks the specified object.

This action does not have any parameter.

Example:Click

StorePropertyValue

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

Some Android and iOS properties are not accessible.

List of accessible properties for Android: "name", "contentDescription", "className", "resourceId", "text", "enabled", "checkable", "checked", "clickable", "focusable", "focused", "longClickable", "scrollable", "selected", "displayed"

List of accessible properties for iOS: "name", "value", "label", "hint"

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example: StorePropertyValue                            "key"                     "text"

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example: SetFocus

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or false.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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"

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example ClickAt        "5"            "10"

IsSelect

This action verifies whether the specified radio button is selected or not.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

state

Value of this parameter can be True or false.

  • Set True if you want to check the selection.
  • Set False if you want to check the deselection.

No

String

Example: IsSelect                        "True"

Select

This action selects the specified radio button.

This action does not have any input parameter.

Example: Select

SelectByIndex

This action selects the specified radio button based on its index number. The index starts from 1. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

groupName

Enter the group name under which the radio button to be selected belongs to. This is the name attribute in html.

Yes

String

index

Enter the index of the radio button from the group which you want to select. Index starts at 1

No

String

Example:

SelectByIndex               "Selection"               "3"

SelectByValue

This action selects the specified check box based on its value. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value of the check box to be selected. 

Yes

String

groupNameEnter the group name to which the check box belongs to. This is the name attribute in html.YesString

Example:
SelectByValue                             "Occupation"

SelectIfTrue

This action selects the radio button, only if the parameter passed is True.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

check

Value for this parameter can be True or false. 

No

True

Example: SelectIfTrue          "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"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:
StoreChildCount                               "Key"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS

ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:
ClickAction

DoubleClick

This action double-clicks the specified web element.

Example:

DoubleClick

DownloadFile

This action clicks the link/element that opens a download window, which is used to download the files. You need to handle the action externally as it does not wait until the file is downloaded.

Qualitia uses its internal mechanism to handle the Download File pop-up screen.

You can also use AutoIT to execute this action on Windows operating systems only. You need to install AutoIT.

After installing AutoIT, you can configure the AutoIT Install path in Qualitia client as follows: Project Configuration > General > Settings > AutoIT Install Path. The default AutoIT path is C:\Program Files (x86)\AutoitV3.

To configure the AutoIT Path for an offline suite:

  • Open the Qualitia Offline Configuration Manager.
  • Select the Offline Suite and the associated execution profile.
  • Click Qualitia Settings > General > AutoIT Path.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

folderPath

The path where the file is to be download. Please check Table 1 "Parameter Mandate" to validate in the situation where this parameter will be mandatory. In case the parameter Mandatory; the user should take care that the folder path exists. The action does not validates whether the folder exist

Yes

String

Filename

The filename of the downloadable file, to be given incase the user requires to give specific name and not depend on the default name of the file. In case, the file already exist, similar window like below will appear. Such windows are not handled by the action. Incase, the user does not provide this data, the action will pick the default file name available while download.

No

String

 Example:



Example 

DownloadFile               "C:/ProgramData"           "Qualitia" 

DragAndDropToOffset

This action drags and drops the specified web element at the specified location. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

Yes

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

Yes

String

Example:

DragAndDropOffset            "100"              "500"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example:

MouseDown                 "5"           "10"

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret. 


Input Parameters:

Parameter Name
Parameter Description
Mandatory
Data Type
arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

YesArray

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

UP

~{UP~}

TAB

~{TAB~}

SUBTRACT

~{SUNSTRACT~}

SPACE

~{SPACE~}

SHIFT

~{SHIFT~}

SEPARATOR

~{SEPARATOR~}

SEMICOLON

~{SEMICOLON~}

RIGHTCLICK

~{CONTEXTCLICK~}

RIGHT

~{RIGHT~}

RETURN

~{RETURN~}

PAUSE

~{PAUSE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

NUMPAD9

~{NUMPAD9~}

NUMPAD8

~{NUMPAD8~}

NUMPAD7

~{NUMPAD7~}

NUMPAD6

~{NUMPAD6~}

NUMPAD5

~{NUMPAD5~}

NUMPAD4

~{NUMPAD4~}

NUMPAD3

~{NUMPAD3~}

NUMPAD2

~{NUMPAD2~}

NUMPAD1

~{NUMPAD1~}

NUMPAD0

~{NUMPAD0~}

NULL

~{NULL~}

MULTIPLY

~{MULTIPLY~}

META

~{META~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

LEFT_ALT

~{LEFT_ALT~}

LEFT

~{LEFT~}

INSERT

~{INSERT~}

HOME

~{HOME~}

HELP

~{HELP~}

F12

~{F12~}

F11

~{F11~}

F10

~{F10~}

F9

~{F9~}

F8

~{F8~}

F7

~{F7~}

F6

~{F6~}

F5

~{F5~}

F4

~{F4~}

F3

~{F3~}

F2

~{F2~}

F1

~{F1~}

ESCAPE

~{ESCAPE~}

EQUALS

~{EQUALS~}

ENTER

~{ENTER~}

END

~{END~}

DOWN

~{DOWN~}

DOUBLECLICK

~{DOUBLECLICK~}

DIVIDE

~{DIVIDE~}

DELETE

~{DELETE~}

DECIMAL

~{DECIMAL~}

CONTROL

~{CONTROL~}

COMMAND (META)

~{COMMAND~}

CLICK

~{CLICK~}

CLEAR

~{CLEAR~}

CANCEL (Esc)

~{CANCEL~}

BACK_SPACE

~{BACK_SPACE~}

ARROW_UP

~{ARROW_UP~}

ARROW_RIGHT

~{ARROW_RIGHT~}

ARROW_LEFT

~{ARROW_LEFT~}

ARROW_DOWN

~{ARROW_DOWN~}

ALT

~{ALT~}

ADD

~{ADD~}

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:

SetValueAttribute           "#ff0990"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:

StoreCSSProperty      "Key"      "display"            

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:

StoreLocation        "Height"            "Width"

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name under which you want to store the height of the object.

Yes

String

keyYPosition

Enter the key name under which you want to store the width of the object.

Yes

String

Example:

StoreSize           "Height"                   "Width"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:

StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Input Parameter:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or false.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want to verify that the object is disabled.

Yes

String

Example:

VerifyEnability                          "True"

ClickandchooseOkOnNextConfirmation (Deprecated)

This action handles the alert or confirmation that comes up post clicking the OK button. This action fails if the button is clicked and no alert or confirmation comes up.

This action does not have any parameter.

Example:

ClickandchooseOkOnNextConfirmation

WaitForSelectionStateToBe

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedSelectionState

Enter the expected selection state. Set True for selection and False for deselection.

Yes

Boolean

timeOut

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

No

Integer

pollingInterval

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

No

Integer

keySelectionState

Enter the key name under which the status of this step will be stored. 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. Default value is Fail. You can override this with Defect.

No

String

Example:
WaitForSelectionStateToBe          "False"        "5"          "500"       "Key"       "Defect"

WaitForSelection

This action waits till the specified object gets selected. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

Integer

pollingInterval

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

No

Integer

keySelection

Enter the key name under which the status of this step will be stored. 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. Default value is Fail. You can override this with Defect.

No

String

Example:

WaitForSelection      "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:
WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:

WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

Integer

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

Integer

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.


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. 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     "5"          "500"     "Key"       "Defect"

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

ClickandWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time in the associated execution profile.

The default value is 20 seconds. If the page loads before reaching the maximum sync time execution continue to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in the ready state. If it is in a ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document load in a ready state and assume that the page is loaded could however not work as expected at all times.

ClickandchooseOkOnNextConfirmation (Deprecated)

This action handles the alert or confirmation that comes up post clicking the OK button. This action fails if the button is clicked and no alert or confirmation comes up.

This action does not have any parameter.

Example:

ClickandchooseOkOnNextConfirmation

WebTable Actions

Click

This action clicks the specified object.

This action does not have any parameter.

Example:

Click

ClickAction

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ActionClick uses underlying selenium WebDriver "Action" class to perform click action. Qualitia recommends using this action for web applications.

Example:

ClickAction

ClickAt

This action clicks at the specified point on the object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

ClickAt        "5"            "10"

ClickCell

This action clicks the specified cell from the table.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

row

Enter the row number of the cell which you want to click. Row number starts at 1.

Yes

String

column

Enter the column number of the cell which you want to click. Column number starts at 1.

Yes

String

Example

ClickCell               "5"                   "10"

ClickImageInCell

This action clicks the image from the specified cell. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

altorindex

Enter any of the attribute of the image. This can be alt or title. This parameter can also be an index. Index starts from 1. Following will be the preference in which the action will assume the incoming data: If the data is a number then it will be considered as index, else, the first preference then goes to title. If an image with specified title is found then click, otherwise, search for an image with property. Alt = incoming data

Yes

String

Row

Enter the row number of the cell in which the image is present. Row number starts at 1.

Yes

String

Column

Enter the column number of the cell in which the image is present.

Yes

String

Example:

ClickImageInCell              "2"                "2"           "3"

ClickJS

This action clicks the specified object from the web application under test.

This action does not have any parameter.

Note: ClickJS uses javascript code to perform the click action. Qualitia recommends using this action for web applications.

Example:

ClickJS


ClickJSAndSelectWindowUsingURL

This action is used to click the web element or object that opens single or multiple windows from which a specific window is selected.
This action accepts 'waitTimeForWindow' for the specific window to open.

This action is used in the following 2 scenarios:

  • When a single window opens after clicking the web element/object, you need to give only 'waitTimeForWindow' parameter. 
  • When multiple windows open after clicking the web element or object, then you can provide the exact URL or regex patterned URL  window. You must give the URL and 'isURLPatternString' parameters.
    Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

waitTimeForWindow

Enter the wait time for the window to open.

Yes

String

URL

Enter a specific URL or regex pattern of URL for the window you want to select.

NoString
isURLPatternString

Enter one of the following:

  • True: If you want to apply the regex pattern to URL.
  • False: If you do not want to apply the regex pattern to URL.
NoString

Example 1

String waitTimeForWindow : "5",

String url : null(do not give any value)

String isURLPatternString : null(do not give any value)

Expected Result - Here you do not need to provide URL or isURLPatternString as after clicking the object or element opens. The action waits up to 5 seconds for the window to appear after clicking the web element or object and then select the window.

Example 2

String waitTimeForWindow - "5",

String url - "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?                                                             lkfm=editPage&lknm=cas3&lktp=003&lksrch=",

String isURLPatternString - "False",

The action waits for up to 5 seconds for multiple windows to appear after clicking web element or object and it selects the window with the url "https://bflsme--preprod.cs57.my.salesforce.com/_ui/common/data/LookupPage?lkfm=editPage&lknm=cas3&lktp=003&lksrch=". As the isURLPatternString parameter is 'false' , the action finds as per the given URL.  

Example 3

String waitTimeForWindow - "5",

String url - "www.([A-Z])\w+",

String isURLPatternString - "True",

Expected Result - The action waits for up to 5 seconds for multiple windows to open after clicking web element/object and it selects the window which matches the regex pattern  "www.([A-Z])\w+" as provided in the URL parameter. As the isURLPatternString parameter is 'True', the action treats the URL parameter as a regex pattern. In case there are multiple windows satisfying the regex pattern, the action selects the first window.

ClickLinkAtCell

This action clicks the link present in the specified cell.

This is applicable for tables having same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Link

Enter the URL to be clicked.

No

String

Row

Enter the row number of the cell in which the link is present. Row number starts at 1

Yes

String

Column

Enter the column number of the cell in which the link is present. Column number starts at 1

Yes

String

Example:

ClickLinkAtCell              "http://www.google.com"             "2"          "3"

If Link is an empty data ("" or $NULL$), and there are multiple links in the cell, then the first link in the cell will be clicked. If there is only one link in the cell, then the link will be clicked. However, if there is no link available in the cell, the action will fail with an error message that no link is available in the cell.

ClickLinkTitleAtCell

This action clicks a link based on the title in the specific cell of the table. This is applicable for tables having same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Link

Enter the link title which you want to click.

No

String

Row

Enter the row number of the cell from the link is to be clicked. Row number starts at 1.

Yes

String

Col

The column number of the cell from which the link is to be clicked. Column number starts at 1.

Yes

String

Example:

ClickLinkTitleAtCell         "google"       "2"      "3"

Note: If Link is an empty data ("" or $NULL$), and there are multiple links in the cell, then the first link in the cell will be clicked. However, if there is no link available in the cell, the action will fail with an error message that no link is available in the cell.

ClickRadioButtonInCell

This action clicks a radio button in the specified cell of the table. This can also be applicable for tables where each row in the table has different number of columns.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

row

Enter the row number of the cell from which you want to click the radio button. Row number starts at 1.

Yes

String

column

Enter the column number of the cell from which you want to click the radio button. Column number starts at 1.

Yes

String

Example: ClickRadioButtonInCell                "2"            "3"

CompareColumnData

This action compares the entire record in the specified column with the expected array data.

This is only applicable for tables having the same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Column

Enter the column number of table from which you want to compare the data. Column starts from 1.

Yes

String

columnData

Enter the entire column data expected to be present in a specified column. Separate multiple items with carat (^) operator. 

No

Array

Example:

Consider a table containing the data India, Australia, England in Column 4. If this data needs to be verified, the action can be used as follows:

CompareColumnData  "4"   "India~^Australia~^ England"

CompareRowData

This action compares the entire record in the specified row with the expected array data.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number from which you want to compare the data. Row number starts from 1.

Yes

String

rowData

Enter the entire row data expected to be present in a specified row. Separate multiple items with carat (^) operator.

No

Array.

Example:

Consider a table containing the data India, Australia, England in row 2. If this data needs to be verified, the action can be used as follows.

CompareTableRowData  "2"  "India~^Australia~^ England"

DeSelectCheckBoxInCell

This action deselects the check box from the specified table cell. This can also be applicable for tables where each row in the table have different number of columns.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number from where you want to select the check box. Row number starts at 1.

Yes

String

Column

Enter the column number from where you want to select the check box. Row number starts at 1.

Yes

String

Example:

DeSelectCheckBoxInTableCell                                    "2"          "5"

This will deselect the check box present in the second row and the fifth column cell in the table. If the check box is already deselected then the action will pass.

DoubleClick

This action double-clicks the specified web element.

This action does not have any parameter.

Example:

DoubleClick

DragAndDrop

This action drags and drops the specified web element at the specified location. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

offsetX

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as +100,100 , -100, 10, and so on.

No

String

offsetY

Enter the offset in pixels from the current location to which the element should be moved. The offset parameter can be as -100,100 , +100, and so on.

No

String

Example:

DragAndDrop            "100"              "500"

MouseDown

This action simulates left-click at the specified location on the screen.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example:

MouseDown                 "5"           "10"

MouseOver

This action simulates a mouse hovering over the specified object.

This action does not have any parameter. 

Example:

MouseOver

MouseUp

This action simulates the event that occurs when the user releases the mouse button.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

X

The x-coordinate of the click.

No

String

Y

The y-coordinate of the click.

No

String

Example

MouseUp         "5"          "10"

RightClick

This action right-clicks the specified web element.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

option

The context menu option number that needs to be clicked.

No

String

Example:

RightClick             "3''

This will select the third option from the context-menu.

ScrollIntoView

This action scrolls to view the specified object. 

This action does not have any parameter. 

Example:

ScrollIntoView

SecureSetTextinCellEdit

This action sets the specified text in the specified cell of the table. Once you move focus from the cell, Qualitia encrypts the text for security purpose.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number of the cell in which you want to enter the text. Row number starts at 1.

Yes

String

Column

Enter the column number of the cell in which you want to enter the text. Column number starts at 1.

Yes

String

text

Enter the text which you want to add in the cell in the specified format.
Format: Encrypt(<TEXT TO BE ADDED>)

No

String

Example:

SecureSetTextinCellEdit        "3"            "2"        "Encrypt(Abc)"

When the focus is moved away from the parameter, Qualitia will automatically encrypt the data ABC and result in a secured text like "vHpmlfI4R3PQkCN4sZnuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

SelectCheckboxInCell

This action selects a check box from the specified cell of the table. This can also be applicable for tables where each row in the table have different number of columns.

This step will pass if the check box is already selected.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number of the cell from which you want to select the checkbox. Row number starts at 1.

Yes

String

column

Enter the column number of the cell from which you want to select the checkbox. Column number starts at 1.

Yes

String

Example:

SelectCheckboxInCell          "2"         "3"

SendKeySequence

This action sends one or multiple keys specified in the parameters to the specified object. You may use the syntaxes mentioned below to send normal or modifier keys. Multiple keys should be separated by caret.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

arrayofKeys

Enter the keys you want to send.

In case you want to send a string with modifier characters (from the table mentioned below) you must use caret (^) sign as a separator between modifier characters and normal string values.

Yes

Array

Adding modifiers like SHIFT, Control, and so forth perform the activity of pressing these keys only. For releasing these keys, you must add these modifiers again based on requirements as shown in the example.

Example:
sendKeySequence               "~{SHIFT~}^w^~{SHIFT~}^elcome"

The example above will press the word Welcome. Apart from the normal alphabets, you can also send the modifier keys. When sending modifier keys, you have to send them in the syntax given.

Key

Syntax

NULL

~{NULL~}

CANCEL (Esc)

~{CANCEL~}

HELP

~{HELP~}

BACK_SPACE

~{BACK_SPACE~}

TAB

~{TAB~}

CLEAR

~{CLEAR~}

RETURN

~{RETURN~}

ENTER

~{ENTER~}

SHIFT

~{SHIFT~}

LEFT_SHIFT(SHIFT)

~{LEFT_SHIFT~}

CONTROL

~{CONTROL~}

LEFT_CONTROL(CONTROL)

~{LEFT_CONTROL~}

ALT

~{ALT~}

LEFT_ALT

~{LEFT_ALT~}

PAUSE

~{PAUSE~}

ESCAPE

~{ESCAPE~}

SPACE

~{SPACE~}

PAGE_UP

~{PAGE_UP~}

PAGE_DOWN

~{PAGE_DOWN~}

END

~{END~}

HOME

~{HOME~}

LEFT

~{LEFT~}

ARROW_LEFT

~{ARROW_LEFT~}

UP

~{UP~}

ARROW_UP

~{ARROW_UP~}

RIGHT

~{RIGHT~}

ARROW_RIGHT

~{ARROW_RIGHT~}

DOWN

~{DOWN~}

ARROW_DOWN

~{ARROW_DOWN~}

INSERT

~{INSERT~}

DELETE

~{DELETE~}

SEMICOLON

~{SEMICOLON~}

EQUALS

~{EQUALS~}

NUMPAD0

~{NUMPAD0~}

NUMPAD1

~{NUMPAD1~}

NUMPAD2

~{NUMPAD2~}

NUMPAD3

~{NUMPAD3~}

NUMPAD4

~{NUMPAD4~}

NUMPAD5

~{NUMPAD5~}

NUMPAD6

~{NUMPAD6~}

NUMPAD7

~{NUMPAD7~}

NUMPAD8

~{NUMPAD8~}

NUMPAD9

~{NUMPAD9~}

MULTIPLY

~{MULTIPLY~}

ADD

~{ADD~}

SEPARATOR

~{SEPARATOR~}

SUBTRACT

~{SUNSTRACT~}

DECIMAL

~{DECIMAL~}

DIVIDE

~{DIVIDE~}

F1

~{F1~}

F2

~{F2~}

F3

~{F3~}

F4

~{F4~}

F5

~{F5~}

F6

~{F6~}

F7

~{F7~}

F8

~{F8~}

F9

~{F9~}

F10

~{F10~}

F11

~{F11~}

F12

~{F12~}

META

~{META~}

COMMAND (META)

~{COMMAND~}

ZENKAKU_HANKAKU

~{ZENKAKU_HANKAKU~}

CLICK

~{CLICK~}

DOUBLECLICK

~{DOUBLECLICK~}

RIGHTCLICK

~{CONTEXTCLICK~}

SetFocus

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

SetTextinCellEdit

This action sets text in the specified cell of the table.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number of the cell in which you want to enter the data. Row number starts at 1.

Yes

String

Column

Enter the column number of the cell in which you want to enter the text. Column number starts at 1.

Yes

String

text

Enter the text you want to enter in the cell.

No

String

Example:

SetTextinCellEdit                     "3"           "2"        "Qualitia"

SetValueAttribute

This action sets the data specified in the 'value' attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

value

Enter the value to be added for the Value attribute.

Yes

String

Example:

SetValueAttribute           "#ff0990"

StoreCellText

This action stores the text of the specified table cell under the specified key. The key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

The variable name in which the cell text is to be stored.

Yes

String

Row

The row number of the cell. Row number starts at 1.

Yes

String

Column

The column number of the cell. Column number starts at 1.

Yes

String

Example:

StoreCellText             "cellTextKey"                "1"              "3"

StoreChildCount

This action stores the child count of the specified 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 child count will be saved.

Yes

String

Example:

StoreChildCount                               "Key"

StoreColumnCount

This action stores the column count of the specified table under the specified key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the variable name to store table's column count.

Yes

String

row

Enter the row number whose column count you want to store.

Yes

String

Example:

StoreColumnCount                   "key"           "2"

StoreColumnData

This action stores the column data of the specified column number. This is only applicable for tables having same number of columns in all the rows.

The data is separated by caret (^). 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store the column number.

Yes

String

column

Enter the column number of the cell whose data you want to store. Column number starts at 1.

Yes

String

Example:

StoreColumnData        "key"         "2"

StoreColumnNumber

This action stores the column number with the specified column name. This is only applicable for tables having same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store the column name.

Yes

String

columnName

Enter the column name whose number you want to store. 

No

String

Example:

StoreColumnNumber            "key"         "Column 1"

StoreCSSProperty

This action stores the CSS property value of the object under the specified key. Key value can be retrieved using the key name. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyProperty

Enter the key name under which the property value will be stored. 

Yes

String

propertyEnter the property name whose value you want to store.YesString

Example:

StoreCSSProperty         "Key"      "display"       

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"

StoreInstanceOfDataFromColumn

This action stores the number of occurrences of the specified data in columns. The data comparison is case-sensitive.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the occurrences.

Yes

String 

Column

Enter the column number where you want to search the data. Column number starts at 1.

Yes

String

Data

Enter the data you want to search in the specified column.

No

String

Example:

StoreInstanceOfDataFromColumn          "result"        "3"         "Qualitia"

StoreLocation

This action stores the current location of the object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyXPosition

Enter the key name to store the height of the location of the object.

Yes

String

keyYPosition

Enter the key name to store the width of the location of the object.

Yes

String

Example:
StoreLocation        "Height"            "Width"

StorePropertyValue

This action stores the property of the specified object under the key name. The stored 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 property value will be stored.

Yes

 String

Property

Property/attribute name whose value needs to be stored under the specified key. This can be any accessible property of Android/iOS native object mentioned above.

Yes

 String

Example:

StorePropertyValue                            "key"                     "text"

StoreRowCount

This action stores the row count of the specified table under the specified key.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store table's row count.

Yes

String

Example:

StoreRowCount                          "Key"

StoreRowData

This action stores the data from the specified row number.

The data is separated by caret (^). 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store data from row. 

Yes

String

row

Enter the row number of the cell whose data you want to store. Row number starts at 1.

Yes

String

Example:

StoreRowData                           "key"     "2"

StoreRowNoContainingCellText

This action stores the row number of the cell whose data contains the text specified by the user. This comparison is case-sensitive . When multiple cells in the column specified contain the expected data, then the first-row number shall be stored in the variable. This can also be applicable for tables where each row in the table has a different number of columns. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which the row number will be stored.

Yes

String

cellText

Enter the cell data you want to search in the table.

No

String

Column

Enter the column number of the cell in which the data is present.

Yes

String

Example:

StoreRowNoContainingCellText                "key"           "word"         "2"

StoreRowNoContainingTextInArray

This action finds the cell that contains the specified combination of the texts in the specified column.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the row number. 

Yes

String

cellText

Enter the text combination which you want to check in the columns.

Note 1: The text combination is case-sensitive.

Note 2: If you want to find multiple text combinations, then you can separate with ^. For example, if you specify John^Smith, the action finds the first cell that contains both John and Smith. Hence, in this case the first cell that has values in any sequence such as John W Smith and Smith A John will be considered.

Note 3: If you do not enter any value, the empty string “” is used as the cell text value during the execution. The action starts from the top of the specified column to find the cell that matches the specified condition. When the first cell matching the condition is found, the action stores the associated row number of the cell into the Key parameter.

No

Array

Col

The column number of the cell in which you want to search the combination of data. Column number starts at 1

Yes

String

Example:

StoreRowNoContainingTextInArray                             "rowNo"        "John^Smith"       "3"

In this case, this action finds the cell in column 3 of the selected table that contains texts John and Smith. The rowNo stores the row number of the cell that contains a combination of the specified texts.

StoreRowNoOfCellText

This action stores the row number of the cell having the specified data in a specified column. This comparison is case-sensitive. When multiple cells in the column specified contain the expected data, then the first row number is stored under the specified key. This is also applicable for tables where each row in the table has different number of columns.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

The variable in which the row number is to be stored.

Yes

String

cellText

Cell data to be searched for in the table.

No

String

Column

Column number of the cell data to be searched for. Column number starts at 1.

Yes

String

Example: StoreRowNoOfCellText                           "key"                   "Testing"             "2"

StoreRowNumberContainsMaximumValue

This action stores the row number of the table which contains the maximum value of String data in the column specified by user.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the row number.

Yes

String

Col

Enter the column number where search for the maxmum value. Column number starts at 1.

Yes

String

Example: StoreRowNumberContainsMaximumValue                 "rowNumber"                 "2"

StoreRowNumberHavingMinCellDataincolumn

This action stores the row number of the table which contains the minimum value of String data from the specified column.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the row number.

Yes

String

Col

Enter the column number where search for the minimum value. Column number starts at 1.

Yes

String

Example:

StoreRowNumberHavingMinCellDataincolumn                        "rowNumber"              "4"

StoreRowNumWithRowData

This action stores the row number of the table which contains the specified data.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

rowData

Enter the entire row data expected to be present in a specified row. Separate multiple items with carat (^) operator.

No

Array

Key

Enter the key name under which the row number will be stored.

Yes

String

Example:

Consider a table containing the following data:

  • India is in column 1 of a row,
  • Australia is in column 3 of the same row,
  • England is in column 6 of the same row,

If the row number for this entry is to be retrieved, the action can be used as follows:

StoreRowNumWithRowData     "1^India^3^Australia^6^ England"

Thus it will check the data "India" in the first column of the table, "Australia" in the third column and "England" in the 6th column in a particular row. Thus, the data needs to be present in the same row.

The row number containing this data will get stored in "RowNumber" variable

StoreSize

This action stores the size of the specified object under keys. The key values can be retrieved using key names.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyHeight

Enter the key name under which you want to store the height of the object.

Yes

String

keyWidth

Enter the key name under which you want to store the width of the object.

Yes

String

Example:

StoreSize           "Height"                   "Width"

StoreTableData

This action stores the data of multiple columns of the table into the specified file.

You may use the parameter "noOfPageNext"  if you want to store the data laid out in the table across multiple pages.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

locatorOfPageNext

Enter the locator of the object which is used to navigate to the next page. If the table is not to be navigated, then this parameter can be "". The locator has to be only an XPATH

No

String

columsToStore

Enter the index of columns whose data you want to store in the file. In you want to store multiple columns, separate the column index with the carat (^) operator.

Yes

Array

noOfPageNext

Set the number of times page next needs to be clicked to store the data laid out in a table across multiple pages. If only the current page table data needs to be stored, this parameter should be set as "0".

No

String

fileToStore

Enter the complete path of the file in which you want to store the data. The file types supported are .xml, .xls, and .txt.

Yes

String

Example

StoreTableData                                            "//[@id=":cf"]"        "1^2^3 2"                "0"      "C:\DBResults\Excel\ORACLE\Result.xls"

StoreText

This action stores the text existing inside the specified object under the specified keys. The key values can be retrieved using the key names. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

keyText

Enter the key name to store the text from the specified object.

Yes

String

Example:

StoreText        "Key" 

StoreValueAttribute

This action stores the data present in the "value" attribute of the object.

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a variable to store the data present in the "value" attribute for the object.

Yes

String

Example:
StoreValueAttribute        "Key"

VerifyCellText

This action verifies the actual data of the specified cell with the expected cell data.

This comparison is case-sensitive.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

data

Enter the data which you want to verify in the table cell.

No

String

Row

Enter the row number of the cell. Row number starts at 1

Yes

String

Col

Enter the column number of the cell. Column number starts at 1.

Yes

String

Example: VerifyCellText          "Good Morning"         "2"        "3"

VerifyDataExistenceInColumn

This action verifies the existence of the expected data in the specified column. The expected data can be a sub-list of the actual column data in the table.

This is only applicable for tables having the same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Column

Enter the column number table where you want to verify the data. Column number starts at 1.

Yes

String

columnData

Enter the data to be searched in a column. Separate multiple items with carat (^) operator. 

No

String

existence

Value of this parameter can be either True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.

No

String

Example: VerifyDataExistenceInColumn       "2"            "Test"          "True" 

This will verify if the data Test is present in the column 2 of the table.

VerifyDataExistenceInColumn        "2"            "Test"       "False"

This will verify if the data Test is not present in the column 2 of the table.

VerifyDataExistenceInRow

This action verifies the existence of the specified data in the specified row. The expected data can be a sub-list of the actual column data in the table.

This is only applicable for tables having same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number of the table where you want to verify the existence. Row number starts from 1.

Yes

String

rowData

Enter the data to be searched in a row. Separate multiple data with the caret (^) operator.

No

Array

existence

Value of this parameter can be either True or False.

  • Set True if you want to check for the existence. 
  • Set False if you want to check for the non-existence. 

No

String

Example:

VerifyDataExistenceInRow             "2"        "Test"       "True"

This shall verify if the data Test is present in the row 2 of the table.

VerifyEnability

This action verifies the enability of the specified object. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

enability

Value for this parameter can be True or False.

  • Set True if you want to verify that the object is enabled. 
  • Set False if you want 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

Value for this parameter can be True or False.

  • Set True if you want to check the existence.
  • Set False if you want to check the non-existence.

No

String

Example:

VerifyExistence                      "True"

VerifyImageInCell

This action verifies that the image present in the specified cell is having the specified src/title attribute.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the row number of the cell from which you want to verify the image. Row number starts at 1.

Yes

String

column

Enter the column number of the cell from which you want to verify the image. Column number starts at 1.

Yes

String

SrcTitle

Enter either the src or title data of the image. First the source property will be compared with the actual source and if not present then the title property will be verified.

No

String

Example:

VerifyImageIncell              "4"          "6"         "Review"

VerifyLinkTitleAtCell

This action verifies title of link in the given cell. It does not perform an exact match. It performs a contain match.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

link

Enter the title data of the link.

No

String

row

Enter the row number of the cell in which you want to verify the link. Row number starts at 1.

Yes

String

column

Enter the column number of the cell in which you want to verify the link. Column number starts at 1.

Yes

String

Example

VerifyLinkTitleAtCell                     "ClickHere"              "5"      "10"

VerifyTableRowCount

This action verifies the actual row count of the specified table with the expected row count.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

rowCount

Enter the expected row count which you want to compare with the actual row count. 

Yes

String

Example:

VerifyTableRowCount          "6"

VerifyVisibility

This action verifies the visibility of the specified object.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

visibility

Value for this parameter can be True or False.

  • Set True if you want to check the visibility.
  • Set False if you want to check the invisibility.
    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"

ClickCheckboxInCellTH (Deprecated)

This action selects the check box from the specified header of the table.

This step will pass if the check box is already selected.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Row

Enter the \row number of the cell from which the checkbox is to be clicked. Row number starts at 1.

Yes

String

Column

Enter the column number of the cell from which the checkbox to be clicked. Column number starts at 1.

Yes

String


Example:

SelectCheckboxInCell             "2"              "3"

StoreVisibility 

This action stores the visibility status for a web element under the specified key name in the following conditions:

  • True: If the web element is visible.
  • False: If the web element is not visible.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

strKey

Enter a key to store the visibility status.
No

String

Example: StoreVisibility   "Key"

ClickAndWait (Deprecated)

This action clicks the specified object and waits for the seconds specified in Sync Time under the Configuration Settings (Execution) window.

Default value is 20 seconds. If the page loads before reaching the maximum sync time execution continues to the next steps. 

This action does not have any parameter. 

Example:

ClickAndWait

Webdriver waits for the document to come in ready state. If it is in ready state it is assumed that the page is loaded completely and Webdriver stops waiting. The condition to wait till the document to load in ready state and assume that the page is loaded could however not work as expected at all times.

ClickImageInCellTH (Deprecated)

This action clicks the image in the specified cell of the table. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

alt_title

Enter the attribute of the image alt or title. First preference then goes to title and if an image with specified title is found then click, else, search for an image with property. Alt = incoming data

No

String

Row

Enter the row number of the cell from which the image is to be clicked. Row number starts at 1.

Yes

String

Col

Enter the column number of the cell from which the which the image is to be clicked. 

Yes

String

Example:

ClickImageInCellTH          "2"        "2"       "3"

ClickLinkAtCellandchooseOkOnConfirmation (Deprecated)

This action clicks a link in the specific cell of the table. This is applicable for tables having same number of columns in all the rows. After clicking the link, if an alert or confirmation appears, this action will accept it by clicking OK.

This step fails if the link is clicked and no alert or confirmation appears. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Link

Enter the URL to click.

Yes

String

Row

Enter the row number of the cell where the link is present. Row number starts at 1.

Yes

String

Column

Enter the column number of the cell where the link is present. Column number starts at 1.

Yes

String

Example:

ClickLinkAtCellandchooseOkOnConfirmation               "http://www.google.com"       "2"     "3"

Note: If Link is an empty data ("" or $NULL$), and there are multiple links in the cell, then the first link in the cell will be click. If there are multiple links in the cell with the same text, then the first link will be clicked. However, if there is no link available in the cell, the action will fail with an error message that no link is available in the cell.

ClickLinkAtCellTH (Deprecated)

This action clicks a link from the specific cell of the table header. This is applicable for tables having same number of columns in all the rows.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Link

Enter the link to click.

No

String

Row

Enter the row number of the cell from the link is to be clicked. Row number starts at 1.

Yes

String

Col

The column number of the cell from which the link is to be clicked. Column number starts at 1

Yes

string

Example:

ClickLinkAtCellTH                         "http://www.google.com"                   "2"                "3"

Note: If Link is an empty data ("" or $NULL$), then the first link in the cell will be click. If there are multiple links with the same text then the first link will be clicked. However, if there is no link available in the cell, the action will fail with an error message that no link is available in the cell.

GenerateAndStoreMaximumValue (Deprecated)

This action fetches the column data having the maximum value. It then adds an increment value to it and stores it under the specified key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key

Enter the key name under which you want to store the maximum generated value.

Yes

String

Col

Enter the column number of the cell from which you want to find the maximum data. Column number starts at 1.

Yes

String

incr

Enter the value by which the maximum data found in the column is to be incremented/decremented.
If this value is "" empty string, then the default increment is 0.

No

String

Example:

GenerateAndStoreMaximumNumber               "key"            "3"              "2"

WaitForAttributeContains

This action waits till the value of the specified attribute changes to the expected partial value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the partial expected partial attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueContains

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeContains      "id"           "we323es"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotContains

This action waits until the specified attribute's value of the object changes to other than the partial parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.   

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the unexpected value before exhausting timeout.

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeValueContains      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBe

This action waits until the specified attribute's value of the object changes to other than the exact parameterized value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the value which should not be there in the attribute value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the value to change. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValueNotToBe

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBe      "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeNotToBeEmpty

This action waits until the specified attribute's value of the object gets filled with some value. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeNotToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"

WaitForAttributeToBe

This action waits till the value of the specified attribute changes to the exact expected value. This comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

attributeValue 

Enter the exact expected value.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected value. 

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for existence of the expected value before exhausting timeout. 

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:

WaitForAttributeToBe         "id"           "232waf"        "5"          "500"     "Key"       "Defect"

WaitForAttributeToBeEmpty

This action waits until the specified attribute's value of the object gets empty. You may specify the timeout and polling interval, if required.  

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

attributeName

Enter the attribute name whose value you want to check.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the attribute value to be empty.  

No

String

pollingInterval

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

No

String

keyAttributeValue

Enter the key name under which the status of this step will be stored. 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:
WaitForAttributeToBeEmpty      "id"           "5"          "500"     "Key"       "Defect"
 

WaitForChildElement

This action waits for the child elements of the specified object to appear. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

childLocatorType

Enter the locator type of the object whose child you want to check.

Yes

String

childLocatorValue

Enter the locator value of the child you want to check. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the elements to appear. 

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForChildElement      "id"       "2"         "5"          "500"     "Key"       "Defect"

WaitForClickability

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForClickability     "5"          "500"     "Key"       "Defect"

WaitForExistence

This action waits for the existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

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

No

String

pollingInterval

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

No

String

keyExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForExistence     "5"          "500"     "Key"       "Defect"

WaitForInnerTextContains

This action waits for the object to contain the expected partial text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerTextContains

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextMatchesPattern

This action waits for inner text from the specified object to match the expected text regular expression pattern. The comparison is case-sensitive. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerTextRegXPattern

Enter the expected pattern for the inner text. Pattern should be regular expression. Step fails in case the pattern is invalid.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextMatchesPattern           ".[My]text."       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotContains

This action waits until the specified attribute's value of the object changes to other than the parameterized value. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the attribute value. 

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the inner text to disappear.    

No

String

pollingInterval

Enter the frequency (in milliseconds) after which you want to check for the expected text to be disappeared before exhausting timeout. 

No

String

keyInnerTextNotContains

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotContains          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextNotToBe

This action waits till the inner text of the object changes from the specified text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the text which should not be there in the object.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the text to change.   

No

String

pollingInterval

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

No

String

keyInnerTextNotToBe

Enter the key name under which the status of this step will be stored. 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:
WaitForInnerTextNotToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInnerTextToBe

This action waits for the object to contain the expected exact text. The comparison is case-sensitive. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

innerText

Enter the expected text you want to wait for.

Yes

String

timeOut

Enter the timeout (in seconds) to wait for the expected text.   

No

String

pollingInterval

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

No

String

keyInnerText

Enter the key name under which the status of this step will be stored. 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:

WaitForInnerTextToBe          "Connect"       "5"       "500"     "Key"       "Defect"

WaitForInvisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

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. 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     "5"          "500"     "Key"       "Defect"

WaitForNonClickability

This object waits for the object to become non clickable. You may specify the timeout and polling interval, if required. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the object to become non clickable.     

No

String

pollingInterval

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

No

String

keyNonClickability

Enter the key name under which the status of this step will be stored. 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:
WaitForNonClickability      "5"          "500"     "Key"       "Defect"

WaitForNonExistence

This action waits for the non existence of the specified object. You may specify the timeout and polling interval, if required. 

Note:

The WaitForNonExistence action passes even if you specify an invalid XPath but with correct syntax. As per the default behavior, Qualitia Automation Studio assumes that the specified path is valid and the object does not exist. Hence it returns a pass result.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the non existence of the object.   

No

String

pollingInterval

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

No

String

keyNonExistence

Enter the key name under which the status of this step will be stored. 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:

WaitForNonExistence     "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBe

This action waits for the number of elements of the specified object locator on the page to be same as the expected number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

Note: The default value is 1.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumberOfElements

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBe       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeLessThan

This action waits for the number of elements of the specified object locator on the page to be less than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

 Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:

WaitForNumberOfElementsToBeLessThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForNumberOfElementsToBeMoreThan

This action waits for the number of elements of the specified object locator on the page to be more than the specified number. You may specify the timeout and polling interval, if required.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

expectedNumOfElements

Enter the expected number of elements to wait for.

No

String

timeOut

Enter the timeout (in seconds) to wait for the number elements to appear. 

No

String

pollingInterval

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

No

String

keyNumOfElementsLessThan

Enter the key name under which the status of this step will be stored. 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:
WaitForNumberOfElementsToBeMoreThan       "2"         "5"          "500"     "Key"       "Defect"

WaitForStaleness

This action waits until the element gets detached from the DOM. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeOut

Enter the timeout (in seconds) to wait for the value to be detached.  

No

String

pollingInterval

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

No

String

keyStatus

Enter the key name under which the status of this step will be stored. 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:

WaitForStaleness        "5"          "500"     "Key"       "Defect"

WaitForVisibility

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

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

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. 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     "5"          "500"     "Key"       "Defect"

WaitForObject (Deprecated)

This action waits for the object to appear or disappear for the maximum number of seconds specified.

If the object is found or not found before the maximum time specified, execution continues to the next steps.

If the wait time is "" then the wait time shall be the "Sync Time" set under the associated execution profile.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.
  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Timeout

Enter the number of seconds to wait for the object to appear or disappear. This has to be 0 or any positive number.

No

String

existence

Value for this parameter can be True or False.

  • Set True if you want to check for the appearance of the object.
  • Set False if you want to check for the disappearance of the object.

No

String

Example:

WaitForObject           "10"            "True"

The action waits for maximum 10 seconds for the object to appear. If the object appears before 10 seconds elapses, execution continues to the next steps.

WaitForObject         "15"          "False"

The action shall wait for maximum 15 seconds for the object to disappear. If the object disappears before 15 seconds elapses, the execution continues to the next steps.

Web Services Actions

API Actions

Qualitia Automation Studio contains the following actions to execute API services.

  • REST.Request.RemoveGenericHeaders

  • REST.Request.ResetGenericHeaders

  • REST.Request.SetHeaders

  • REST.Request.SetQueryParameters

  • REST.Request.ClearQueryParameters

  • REST.Auth.Basic

  • REST.Auth.Digest

  • REST.Auth.Bearer

  • REST.Auth.JWT

  • REST.Request.SetTimeout

  • REST.Request.WaitForAttribute

  • REST.Request.SetFormUrlEncodedParameters

  • REST.Request.ImportSSLCertificate

  • REST.GET.ExecuteAPI

  • REST.POST.ExecuteAPI

  • REST.PUT.ExecuteAPI

  • REST.PATCH.ExecuteAPI

  • REST.DELETE.ExecuteAPI

  • REST.GET.ExecuteAPIFormData

  • REST.POST.ExecuteAPIFormData

  • REST.PUT.ExecuteAPIFormData

  • REST.DELETE.ExecuteAPIFormData

  • REST.GET.ExecuteAPIDownloadRawData

  • REST.PUT.ExecuteAPIDownloadRawData

  • REST.POST.ExecuteAPIDownloadRawData

  • REST.DELETE.ExecuteAPIDownloadRawData

  • REST.Response.StoreStatusCode

  • REST.Response.StoreHeaders

  • REST.Response.StoreHeaderValue

  • REST.Response.VerifyStatusCode

  • REST.Response.VerifyHeaders

  • REST.Response.StoreResponseTime

  • REST.Response.CompareResponseTime

  • REST.ExecuteService (Deprecated)

  • REST.ExecuteAPIService (Deprecated)

  • SOAP.ExecuteService

Before executing Rest API services, ensure that you configure the header parameters in the Rest Generic Headers tab of Project Settings.

To execute Rest API services through the offline suite, you need to open the Qualitia Offline Configuration Manager and add or edit the values in RestGenericHeaders tab. For information about setting these parameters for executing test cases using Qualitia offline package, refer to the Configuring the Settings for an OfflineSuite.

REST.Request.RemoveGenericHeaders

This action helps you skip the generic headers you set in the Rest Generic Headers tab of Project Settings.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

HeaderKey

Enter the header key which you want to skip defined in the Rest Generic Headers Settings.

Yes

String

Example:

REST.Request.RemoveGenericHeaders                 "Content-type"

REST.Request.ResetGenericHeaders

This action helps you reset the generic headers which you have skipped earlier in the test case. The sequence of this action must be set post REST.Request.RemoveGenericHeaders.

This action does not have any parameters.

Example:

REST.Request.ResetGenericHeaders

REST.Request.SetHeaders

This action stores key value pair of the header under specified variable (HeaderLabel). Headers stored under the variable then can be used later in the test case using the HeaderLabel (variable name).

You may store multiple headers using test data. This action must be used before executing API service.

Headers set using this action will override the headers set in the Rest Generic Headers tab. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

HeaderLabel

Enter the variable name under which you want to store the key=value pair of the header.

Yes

String

HeaderKey

Enter the header key which you want to set for the API service to be executed.

Yes

String

HeaderValue

Enter the value for the key set above.

Yes

String

Example:

REST.Request.SetHeaders                 "H1"                   "If-Match"                        "a8f34"

REST.Request.SetHeaders                 "H2"                   "accept"                        "application/xml"

(info) Final Output: While considering H2 as a header label, system will override the values provided (accept=application/xml) in the earlier action (REST.SetGenericHeader) while executing the API service

REST.Request.SetQueryParameters

This action helps you set query parameters for the API service you want to execute. Query parameters you set here are applicable only for the API service you use in the step followed by this action. 

You may set multiple query parameters using test data. This action must be used before executing API service.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

QueryKey

Enter the key which you want to set for the API service to be executed.

Yes

String

QueryValue

Enter the value for the key set above.

Yes

String

Example:

REST.Request.SetQueryParameters                          "draftId"                        "1031143439"

REST.Request.ClearQueryParameters

This action clears the query parameters you set earlier in the test case. If you are using more than one web service actions in a single test case, it is important to clear query parameters set earlier (if any) using this action, else, step may fail.

This action does not have any parameters.

Example:

REST.Request.ClearQueryParameters

REST.Auth.Basic

This action helps you set the basic authentication details for the API service you want to execute. Authentication details you provide here are applicable for the entire session of the test case or test suite.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

Username

Enter the username for authentication.

Yes

String

Password

Enter the password for authentication.

Password should be given in the specific format to be encrypted. 

Format: Encrypt(<PASSWORD>)

Yes

String

Example:

REST.Auth.Basic                          "Qualitia"                        "Encrypt(Qualitia123)"

When the focus is moved away from the parameter, Qualitia will automatically encrypt the data ABC and result in a secured text like "vHpmlfI4R3PQkCN4sZnuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

REST.Auth.Digest

This action helps you set the digest authentication details for the API service you want to execute. Authentication details you provide here are applicable for the entire session of the test case or test suite.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

Username

Enter the username for authentication.

Yes

String

Password

Enter the password for authentication.

Password should be given in the specific format to be encrypted. 

Format: Encrypt(<PASSWORD>)

Yes

String

Example:

REST.Auth.Digest                          "Qualitia"                        "Encrypt(Qualitia123)"

When the focus is moved away from the parameter, Qualitia will automatically encrypt the data ABC and result in a secured text like "vHpmlfI4R3PQkCN4sZnuqw==þNWE3ZDdkNjE3N2JmNDM2ODgxMzQwYWI1MTA3YWNjMDc="

REST.Auth.Bearer

This action helps you set the bearer authentication details for the API service you want to execute. Authentication details you provide here are applicable for the entire session of the test case or test suite.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

Token

Enter the token to access API service you want to execute. 

Yes

String

Example:

REST.Auth.Bearer              "haiosehtoiasjgpaodsjcuasworijgdsf"

REST.Auth.JWT

This action helps you set the jwt authentication details for the API service you want to execute. Authentication details you provide here are applicable for the entire session of the test case or test suite.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

Token

Enter the token to access API service you want to execute. 

Yes

String

Example:

REST.Auth.JWT              "haiosehtoiasjgpaodsjcuasworijgdsf"

REST.Request.SetTimeout

This action helps you to set the timeout duration for the API service to be executed. You can use this action when web service takes too long to respond after connecting.

It should be used prior to API service action. Action may fail if the web service takes longer than the specified time.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

timeout

Enter the timeout period in milliseconds. 

Yes

String

Example:

REST.Request.SetTimeout                 "200"

REST.Request.WaitForAttribute

This action waits for the specified attribute to arrive in the response file after executing the service. You can set the maximum time to wait for the JSON value or XML node attribute to arrive in the response file. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

jsonPath/xpath

Enter the JSON or XML path to the attribute whose value you want to check in the API response. 

Yes

String

jsonValue/attribute

Enter the JSON value or XML attribute which you want to check. You may skip adding this parameter if you want to check only json key or xml node. 

No

String

MaxTimeLimit

Enter the time limit until when you want to check for the required data.

Yes

String

TimeUnit

Enter the time unit to be used to set the maximum time limit.

Value for this parameter can be either milliseconds or seconds.

By default, system considers milliseconds when not set. 

No

String

Example:

  • JSON: 

REST.Request.WaitForAttribute            “$.address.postalCode”         ""                     "20"                  "seconds" 

  • XML: 

REST.Request.WaitForAttribute            “//actors/actor[@id='1']”         ""                     "20"                  "seconds"

REST.Request.SetFormUrlEncodedParameters

This action helps you to add the request body data as key value pair in the form of URL encoded format. Qualitia converts the given data into the URL encoded form data. You can give multiple pairs using the test data. In order to use this action to add form data while executing any API service action, you must use this action prior to API service.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name. 

Yes

String

Value

Enter the value for the key mentioned above.

Yes

String

Example:

REST.Request.SetFormUrlEncodedParameters                        "id"                "23950329"

REST.Request.ImportSSLCertificate

This action helps you to import the SSL certificate to use while executing the API service. You must first export the certificate which you want to import while the API service execution.

For more information on how to export the SSL certificate, click here.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

CertificatePath

Enter the absolute path to the certificate file which you have exported. 

No

String

Alias

Enter an alternative name or label that refers to the certificate file which can be used to locate or access it.

Yes

String

Password

Enter the authentication password to access the certificate file. Default password is changeit.

No

String

Example:

REST.Request.ImportSSLCertificate                         "D:\SSLCertificate.cer"                 "SSL"                  "changeit"

REST.GET.ExecuteAPI

This action helps to pull the desired data using GET method while executing the API service. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

This action supports XML or JSON application file types. 

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed. File types supported are XML, HTML, TXT, and JSON. 

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

If the API URL contains query parameters and you want to pass the URL through baseURL and basePath separately then you need to set all the query parameters through REST.Request.SetQueryParameters action.

For example: if the API Url is: https://petstore.swagger.io:443/v2/pet/findByStatus?status=available

Set the query parameter "status=available" through REST.Request.SetQueryParameters action and after that step, add the GET.ExecuteAPI action along with the values of baseURL and basePath parameters as follows:
baseURL: https://petstore.swagger.io:443
basePath: /v2/pet/findByStatus

Example:

REST.GET.ExecuteAPI         “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               ""                "False"             "C:\Users\Qualitia\Request-Cust_List.xml"            "200"

REST.GET.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               "HeaderLebel"                "False"             "C:\Users\Qualitia\Request-Cust_List.json"              "4xx"

REST.POST.ExecuteAPI

This action helps to add the desired data using POST method while executing the API service. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

This action supports XML or JSON application file types. 

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

Optional

String

RequestFilepath

Enter the absolute path to the file from which you want to post the data. File types supported are XML, HTML, TXT, and JSON.

Optional

String

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

Optional

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

Optional

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

Optional

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed. File types supported are XML, HTML, TXT, and JSON.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

Optional

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.POST.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               ""                "False"             "C:\Users\Qualitia\Request-Cust_List.xml"        "2xx,3xx"

REST.POST.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               "HeaderLebel"                "False"             "C:\Users\Qualitia\Request-Cust_List.json"       "200,300"

REST.PUT.ExecuteAPI

This action helps to update the desired data using PUT method while executing the API service. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

This action supports XML or JSON application file types.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

RequestFilepath

Enter the absolute path to the file from which you want to post the data. File types supported are XML, HTML, TXT, and JSON.

No

String

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed. File types supported are XML, HTML, TXT, and JSON.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.PUT.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               ""                "False"             "C:\Users\Qualitia\Request-Cust_List.xml"                   "400"

REST.PUT.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               "HeaderLebel"                "False"             "C:\Users\Qualitia\Request-Cust_List.json"            "2xx,400"

REST.PATCH.ExecuteAPI

This action is supported on Qualitia Automation Studio v8.0.2 and above.

This PATCH API action updates the partial resources, which can be used as an alternative to the PUT API action. Typically, PATCH API actions are light-weight and consume less bandwidth when compared to the PUT API actions.

You can use this action independently or with other REST actions such as:

  • REST.Request.SetGenericHeader·        

  • REST.Request.SetHeaders

  • REST.Request.SetQueryParameters,

  • REST.Auth.Basic/Digest/Bearer/JWT

This action supports both the application file types: XML and JSON.

You can also store the information related to HTTP Status, HTTP REQUEST TIME, and Header, and use them as input values for the remaining steps of the test case.

Parameter Name

Parameter Description

Mandatory

Data

BaseURL

Enter the URL where you want to execute the API service. Also, you can include BasePath in the URL.

Yes

String

BasePath

Enter the base path where you want to execute the API service.

Note: Do not enter any value If the BaseURL includes the base path. 

No

String

RequestFilepath

Enter the absolute path for the request file. The Request file must be in any one of the following formats:

  • HTML

  • TXT

  • JSON

  • XML

No

String

AuthenticationType

Enter any one of the following authentication service type:

  • Basic

  • Bearer

  • JWT

  • Digest.

Note: The associated authentication parameters must be defined in the previous steps.

Do not enter any value if the API service does not use any authentication service. 

No

String

HeaderLabel

Enter the header label if you have specified it in the previous steps of the current test case or task. 

No

String

SSLFlag

Specify whether to consider SSL certificate for executing the API service. 

  • Enter True to consider SSL certificate (default).  

  • Enter False to ignore SSL certificate.

No

String

ResponseFilepath

Enter the absolute path of the file to store the response data.

The response file must be in one of the following formats:

  • HTML

  • TXT

  • JSON

  • XML

Yes

String

ExpectedHTTPStatusCode

After the execution of API service, a specific HTTP status code is returned.

Do one of the following:

  • Enter the expected HTTP status code.

  • Enter the specific HTTP status category if you are not sure of the expected HTTP status. For example, enter the HTTP status code as 1xx, 2xx, and so on.

  • Enter multiple codes or code ranges that you expect by separating with comma. The action passes if the returned HTTP status code matches with any one of the specified code or code range.

No

String

Important Notes:

If the response file extension is XML and the response is returned in JSON, Qualitia Automation Studio converts XML response into JSON and vice-versa.

To store the HTML responses, the ReponseFilePath must contain file path to the *.html file. If the response file extension is not matching with the file format provided by the API service, the response file is saved without any extension. Then, you need to open the Response file using a text editor, such as Notepad.

Example 1:

REST.PATCH.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               ""                "False"             "C:\Users\Qualitia\Request-Cust_List.xml"                   "400"

Example 2: Specifying HeaderLabel and Multiple HTTP status codes.

 REST.PATCH.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               "HeaderLabel"                "False"             "C:\Users\Qualitia\Request-Cust_List.json"            "2xx,400"

REST.DELETE.ExecuteAPI

This action helps to remove the desired data using DELETE method while executing the API service. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

This action supports XML or JSON application file types. 

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

RequestFilepath

Enter the absolute path to the file from which you want to post the data. File types supported are XML, HTML, TXT, and JSON.

No

String

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed. File types supported are XML, HTML, TXT, and JSON.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.DELETE.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               ""                "False"             "C:\Users\Qualitia\Request-Cust_List.xml"            "300"

REST.DELETE.ExecuteAPI          “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            "Basic"               "HeaderLebel"                "False"             "C:\Users\Qualitia\Request-Cust_List.json"            "500,2xx"

REST.GET.ExecuteAPIFormData

This action helps to pull the desired information using GET method while executing the API service with the help of form-data. The form-data can contain one or multiple sets of key-value pairs which will eventually help in executing the specified request method. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.GET.ExecuteAPIFormData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”      "ProjectMapping/OAT”            “Bearer”         "HeaderLabel1”    "True"     “C:\Users\Qualitia\Reponse-Cust_List.json”          "3xx"

REST.POST.ExecuteAPIFormData

This action helps to add desired information using POST method while executing the API service with the help of form-data. The form-data can contain one or multiple sets of key-value pairs which will eventually help in executing the specified request method. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

FormData

Enter the key value pairs of the form data to be used while executing the service. Multiple pairs should be separated by a caret sign (^).

If you want to use file to provide form data, add all the form data in some file and provide absolute path to that file as a parameter. Data in the file should be well formatted.

No

Array

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

Optional

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.POST.ExecuteAPIFormData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”      "ProjectMapping/OAT”           "file=C:\Users\Qualitia\Request-Cust_List.json"        “Bearer”         "HeaderLabel1”    "True"     “C:\Users\Qualitia\Reponse-Cust_List.json”           "3xx"

REST.PUT.ExecuteAPIFormData

This action helps to update desired information using PUT method while executing the API service with the help of form-data. The form-data can contain one or multiple sets of key-value pairs which will eventually help in executing the specified request method. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the base URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

FormData

Enter the key value pairs of the form data to be used while executing the service. Multiple pairs should be separated by a caret sign (^). 

If you want to use file to provide form data, add all the form data in some file and provide absolute path to that file as a parameter. Data in the file should be well formatted.

No

Array

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.PUT.ExecuteAPIFormData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”      "ProjectMapping/OAT”           "file=C:\Users\Qualitia\Request-Cust_List.json"       “Bearer”         "HeaderLabel1”    "True"     “C:\Users\Qualitia\Reponse-Cust_List.json”              "3xx"

REST.DELETE.ExecuteAPIFormData

This action helps to remove desired information using DELETE method while executing the API service with the help of form-data. The form-data can contain one or multiple sets of key-value pairs which will eventually help in executing the specified request method. 

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the base URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

FormData

Enter the key value pairs of the form data to be used while executing the service. Multiple pairs should be separated by a caret sign (^).

If you want to use file to provide form data, add all the form data in some file and provide absolute path to that file as a parameter. Data in the file should be well formatted.

No

Array

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.DELETE.ExecuteAPIFormData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”      "ProjectMapping/OAT”          "file=C:\Users\Qualitia\Request-Cust_List.json"          “Bearer”         "HeaderLabel1”    "True"     “C:\Users\Qualitia\Reponse-Cust_List.json”             "400"

REST.GET.ExecuteAPIDownloadRawData

This action helps to pull the desired information using GET method. You can download raw data file after executing the action giving the desired download location.

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

DownloadLocation

Enter the folder directory location where you want to store the raw data after executing the test case.

No

String


ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.GET.ExecuteAPIDownloadRawData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”        "ProjectMapping/OAT”         “Bearer”         "HeaderLabel1”        "True"       “C:\Users\Qualitia\Reponse-Cust_List.json”            "D:\New Folder\RawDataFiles"               "300"

REST.PUT.ExecuteAPIDownloadRawData

This action helps to update desired information using PUT method. It uses raw data while executing API service. You can download raw data file after executing the action giving desired download location.

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

No

String

RequestFilepath

Enter the absolute path to the file which has REST request-related information. In this file, you can specify the details which you want to update.

No


AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

No

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

No

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

No

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

DownloadLocation

Enter the folder directory location where you want to store the raw data after executing the test case.

No

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

No

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.


Example:

REST.PUT.ExecuteAPIDownloadRawData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”        "ProjectMapping/OAT”         “C:\Users\Qualitia\Request-Cust_List.json”         “Bearer”         "HeaderLabel1”        "True"       “C:\Users\Qualitia\Reponse-Cust_List.json”          "D:\New Folder\RawDataFiles"                      "300"

REST.POST.ExecuteAPIDownloadRawData

This action helps to add desired information using POST method. It uses raw data while executing API service. You can download raw data file after executing the action giving desired download location.

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

Optional

String

RequestFilepath

Enter the absolute path to the file which has REST request-related information. In this file, you can specify the details which you want to add.



AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

Optional

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

Optional

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

Optional

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

DownloadLocation

Enter the folder directory location where you want to store the raw data after executing the test case.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

Optional

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.POST.ExecuteAPIDownloadRawData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”        "ProjectMapping/OAT”         “C:\Users\Qualitia\Request-Cust_List.json”         “Bearer”         "HeaderLabel1”        "True"       “C:\Users\Qualitia\Reponse-Cust_List.json”          "D:\New Folder\RawDataFiles"                  "300"

REST.DELETE.ExecuteAPIDownloadRawData

This action helps to delete desired information using DELETE method. It uses raw data while executing API service. You can download raw data file after executing the action giving desired download location.

This action can work independently or it can be used in a combination of other REST actions like REST.Request.SetGenericHeaders, REST.Request.SetHeaders, REST.Request.SetQueryParameters, REST.Auth.Basic/Digest/Bearer/JWT, based on the test case requirements.

You can also store the information related to HTTP StatusHTTP REQUEST TIME, and Header into the variable and use these values to develop test case flow after executing this action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

BaseURL

Enter the URL where you want to execute the API service.

Yes

String

BasePath

Enter the base path where you want to execute API service. You can include path in the BaseURL parameter itself. In that case, you may keep this parameter blank.

Optional

String

RequestFilepath

Enter the absolute path to the file which has REST request-related information. In this file, you can specify the details which you want to DELETE.



AuthenticationType

Enter authentication type you want to use while executing the API service. Values for this field can be either: Basic, Bearer, JWT, or Digest. Keeping this field blank will be taken as no authentication. For Basic, Bearer, JWT, and Digest authentication types, details will be taken from the previous steps where details are provided.

Optional

String

HeaderLabel

Enter the header label in case you have specified it earlier in the test case/task.  

Optional

String

SSLFlag

Using this parameter, you can decide whether you want to consider SSL certificate while executing the API service.  

  • Use True to consider SSL certificate (default).

  • Use False to ignore SSL certificate.

(warning) External certificate files are not supported.

Optional

String

ResponseFilepath

Enter the absolute path to the file where you want to store the response you get after the service is executed.

Yes

String

DownloadLocation

Enter the folder directory location where you want to store the raw data after executing the test case.

Yes

String

ExpectedHTTPStatusCode

You can give the http status code that you expect at the end of the API service execution. From all the available forty different status code, you can provide any value that you expect. In case you are not sure about the exact expected value, you can also give the category of http status code. For example, 1xx, 2xx, and so forth. Multiple codes or code ranges can be given separated by comma (,).

Optional

String

Important Notes:

If the response file extension is XML and response is in JSON, the system converts XML response into JSON and vice versa.

To store HTML responses, ReponseFilePath should contain file path to .html file. In case the response file extension is not matching with the file format provided by the API, the system stores the response in the file without extension. You can open such files with the help of any text editor like Notepad.

Example:

REST.DELETE.ExecuteAPIDownloadRawData           “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”        "ProjectMapping/OAT”         “C:\Users\Qualitia\Request-Cust_List.json”         “Bearer”         "HeaderLabel1”        "True"       “C:\Users\Qualitia\Reponse-Cust_List.json”          "D:\New Folder\RawDataFiles"                  "300"

REST.Response.StoreStatusCode

This action stores the status of the API service after execution under the specified variable. You can use the status code based on the test case requirements using the variable name. 

This action has to be used immediately followed by the API service action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

key

Enter the variable name under which you want to store the status code of the API service executed. 

Yes

String

Example:

REST.Response.StoreStatusCode                  "Status"

REST.Response.StoreHeaders

This action stores the headers received after the service is executed under the specified variable. You can use the header data based on the test case requirements using the variable name.

This action has to be used immediately followed by the API service action.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

key

Enter the variable name under which you want to store the header data of the API service executed. 

Yes

String    

Example:

REST.Response.StoreHeaders                   "HeaderData"

REST.Response.StoreHeaderValue

This action stores the specified header value from the response given by API service under the specified key. You can then use the stored value based on your test case requirements.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

key

Enter the variable name under which you want to store the header value of the specified key. 

Yes

String

HeaderKey

Enter the header key whose value you want to store from the response header.

Yes

String

Example:

REST.Response.StoreHeaderValue                    "Key"                   "Content-type"

REST.Response.VerifyStatusCode

This action verifies the status of the API service executed against the status specified by the user. This helps in deciding the test case or test suite flow based on the API service status.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

Key

This is the variable name under which the status is stored using the REST.StoreStatusCode action.

Yes

String

ExpectedStatus

Enter the expected status here to verify against the actual status of the API service executed. 

Yes

String

Example:

REST.Response.VerifyStatusCode                    "Status"                      "ExpectedStatus"

REST.Response.VerifyHeaders

This action verifies the header data of the API service executed against the status specified by the user. This helps in deciding the test case or test suite flow based on the header data.

You can give multiple sets of key and value pairs using test data.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

Key

This takes key-value pair .

Example: Content-Type=text/html

Yes

String

 HeaderKey

This is the key from key-value pair that is provided in 1st parameter.

Example: Content-Type

              Yes

            String 

HeaderValue

This is the value from key-value pair that is provided in 1st parameter.

Example: text/html

Yes

String

Example

REST.Response.VerifyHeaders     Content-Type=text/html       Content-Type        text/html

REST.Response.StoreResponseTime

This action helps in storing the response time (in milliseconds) taken by the API service to fetch the response. You can give the desired variable to store the time. The value stored under the variable can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store the time taken to execute the API service in milliseconds. 

Yes

String

Example:

REST.Response.StoreResponseTime         "Key"

REST.Response.CompareResponseTime

This action verifies the response time by comparing the time taken to execute the API service to the expected time according to the specified operator. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

key

Enter the key name under which you want to store the time taken to execute the API service in milliseconds. 

Yes

String

expectedTime

Enter the expected time to compare to the actual time taken to execute the API service.

Yes

String

timeUnit

Enter the time unit using which you want use while storing and comparing the time.

Value for this parameter can be either milliseconds or seconds.

By default, system considers milliseconds when not set. 

No

String

operator

Values for this parameter can be either "< or >".

  • To verify that the response time is lesser than expectedTime, enter < or (default)

  • To verify that the response time is greater than expectedTime, enter >.

No

String

Example:

REST.Response.CompareResponseTime         "Key"                "20"                  "seconds"           "<"

Results:

End of the test case, if the response time in the key is lesser than 20 seconds, test case passes, otherwise test case will report the defect.

REST.ExecuteService (Deprecated)

This action executes the specified REST request. Qualitia gives you provision to store the response at the specified file path location in the JSON format, if required.

You can store the information related to HTTP Status and Header into the variable and use these values to develop test case flow after executing this action.   

URLs with invalid/expired SSL certificates are not supported.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

BaseUrl

Enter the base URL where you want to execute the request.

Yes

String

ApiMethod

Enter the API method you want to execute on the specified URL.

Yes

String

RequestMethod

Enter the method you want to execute on the API url mentioned above.

Yes

String

RequestJsonFilePath

Enter the absolute path to the file which has REST request related information in the JSON format. In this file, you can enter the details which you want to Get, Push and so forth.

No

String

ResultJsonFilePath

Enter the absolute path to the file in which you want to store the REST result.

No

String

AuthenticationType

Enter the authentication type you want to use when executing the REST request. Qualitia supports Basic authentication types.

No

String

UserName

Enter the username if the authentication type selected is Basic.

No

String

Password

Enter the password if the authentication type selected is Basic.

No

String

RequestHeader

Enter the request headers you want to pass when executing the REST request. Multiple headers should be separated by semi colon (;).

No

String

Example:

REST.ExecuteService                “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”      "ProjectMapping/OAT"        “POST”            “C:\Users\Qualitia\Request-Cust_List.json”        “C:\Users\Qualitia\Response-Cust_List.json”         "Basic"        “john.doe@gmail.com”  “john.doe@123”     "Content-Type=application/x-www-;Authentication=Basic fasdhlsdv"

REST.ExecuteAPIService (Deprecated)

This action executes the specified REST request. You can enable or disable the SSL certificate while executing this action. Qualitia gives you the provision to store the response at the specified file path location in the JSON format, if required.

You can store the information related to HTTP Status and Header into the variable and use these values to develop test case flow after executing this action.   

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

URL

Enter the complete REST URL.

Yes

String

RequestMethod

Enter the method you want to execute on the API url mentioned above.

Yes

String

RequestJsonFilePath

Enter the absolute path to the file which has REST request related information in the JSON format. In this file, you can enter the details which you want to Get, Push and so forth.

No

String

ResultJsonFilePath

Enter the absolute path to the file in which you want to store the REST result.

No

String

AuthenticationType

Enter the authentication type you want to use when executing the REST request. Qualitia supports Basic authentication types.

No

String

UserName

Enter the username if the authentication type selected is Basic.

No

String

Password

Enter the password if the authentication type selected is Basic.

No

String

RequestHeader

Enter the request headers you want to pass when executing the REST request. Multiple headers should be separated by semi colon (;).

No

String

SSLCertificateVerification

You can use this parameter to enable or disable the SSL certificate while executing this action.

  • Use True to use SSL certificate. (Default)

  • Use False to ignore SSL certificate.

No

String

Example:

REST.ExecuteAPIService                “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”      "POST”            “C:\Users\Qualitia\Request-Cust_List.json”        “C:\Users\Qualitia\Response-Cust_List.json”         "Basic"        “john.doe@gmail.com”  “john.doe@123”     "Content-Type=application/x-www-;Authentication=Basic fasdhlsdv"             "True"

SOAP.ExecuteService

This action executes the SOAP request in the specified XML file. You can also store response in the XML file, if required.

You can store the information related to HTTP Status and Header into the variable and use these values to develop test case flow after executing this action.

URLs with invalid/expired SSL certificates are not supported.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ServiceUrl

Enter the service URL where you want to execute the request.

Yes

String

SoapAction

Specify the method from your SOAP requests which you want to execute here. 

No

String

RequestMethod

Enter method you want to execute on the specified URL.

Yes

String

RequestXmlPath

Enter the absolute path to the file which has REST request related information in the JSON format. In this file, you can enter the details which you want to Get, Push and so forth.

No

String

ResponseXmlPath

Enter the absolute path to the XML file where the results will be stored.

Yes

String

requestHeaders

Enter the request headers you want to pass when executing the REST request. Multiple headers should be separated by semi colon (;).

No

String

Example:

SOAP.ExecuteService      “https://<HOST_NAME>:<PORT_NUMBER>/<REST_URL>”       "ProjectMapping/OAT"            “POST”         “C:\Users\Qualitia\Request-Cust_List.xml”        “C:\Users\Qualitia\Response-Cust_List.xml”         "Content-Type=application/x-www-;Authentication=Basic fasdhlsdv"

JSON Actions

Qualitia Automation Studio contains the following actions to perform operations on JSON files. 

  • JSON.AddNode

  • JSON.RemoveNode

  • JSON.ConvertStringToFile

  • JSON.ValidateStringSynta

  • JSON.StoreArray

  • JSON.StoreAllUniqueKey

  • JSON.StoreTotalKeyCount

  • JSON.StoreSpecificKeyCount

  • JSON.StoreValue

  • JSON.StoreJsonPathCount

  • JSON.CompareJson

  • JSON.UpdateValueFromJson

  • JSON.UpdateValueInJson (Deprecated)

Also, you can use ValidateStringSyntaxinFile to validates the syntax of XML or JSON file.

JSON.AddNode

This action adds the specified node (key=value pair) in the specified JSON file. 

If you want to add multiple values under the key, you must give values in the correct format accordingly.  

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute file path to the JSON file where you want to add the node.

Yes

String

JSONPath

Enter the JSON path where you want to add the new node. 

Use $ if you want to add node at root level.

Yes

String

JSONKey

Enter the key of the node to be added in the JSON file.

No

String

JSONValue

Enter the value to be added for the key mentioned above.

No

String

JSONValueType

Enter the data type of the value being added as a value.

Value type can be Boolean or Numeric.

Keep the value type blank in case the data type is JSONObject, JSONArray, or String.

No

String

Example: 

  • Adding node with single value:

JSON.AddNode              “C:\Users\Qualitia\Cust_Details.json”        “$.address”         “PostalCode”        "6932331"        "Numeric"

End of the execution, this action add a new node as state and value as California under the node address.

  • Adding node with an array:

JSON.AddNode              “C:\Users\Qualitia\Cust_Details.json”        “$.address”         “StateCode”        "["CA" , "California"]"        ""

End of the execution, this action add a new node as state and value as CA and California under the node address.

JSON.AddNode              “C:\Users\Qualitia\Cust_Details.json”        “$.phoneNumbers”         “ ”        "~{ "type" : "landline", "number": "0123-4567-3263" ~}"        ""

End of the execution, this action add a new node as to display landline number inside the node phoneNumbers.

JSON.RemoveNode

This action removes the specified node from specified JSON file. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute file path to the JSON file from which you want to remove the node.

Yes

String

JSONPath

Enter the node path which you want to remove from the specified file.

This action will remove all the data present inside the node including array.

If JSON path contains array, ensure you use an [] with index. Index starts from 0. 

Yes

String

Example: 

JSON.RemoveNode              “C:\Users\Qualitia\Cust_Details.json”        “$.address.postalCode”

End of the execution, the node postalCode will be removed from the JSON file.

JSON.ConvertStringToFile

This action takes the JSON data given in the parameter and adds it in the specified JSON file.

In case the JSON file does not exist at the specified location, this action creates a new JSON file. Also, if the file contains some data, this action will overwrite old data with new data. 

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

JSONString

Enter the JSON string which you want to add in the JSON file.

Yes

String

OutputJSONFilePath

Enter the directory where you want to store the JSON file. 

Yes

String

Example: 

JSON.ConvertStringToFile              "~{ "firstName": "John", "lastName" : "doe", "age" : 26 ~}"         “C:\Users\Qualitia\Cust_list.json” 

End of the execution, a JSON new file will be added under the specified location with data as provided here.

JSON.ValidateStringSyntax

This action validates the JSON data given in the parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

JSONString

Enter the JSON string which you want to validate.

Yes

String

Example: 

JSON.ValidateStringSyntax           "~{ "firstName": "John", "lastName" : "doe", "age" : 26 ~}" 

End of the execution, if the data is valid, action will pass, else action will fail. 

JSON.StoreArray

This action stores the array data from the specified JSON path under the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute path to the JSON file from which you want to get and store array data.

Yes

String

JSONPath

Enter the JSON path whose data you want to get and store under the specified key.

If JSON path contains array, ensure you use an [] with index. Index starts from 0.

Yes

String

Key

Enter the key under which you want to store the array data.

Yes

String

Example: 

JSON.StoreArray           "C:\Users\Qualitia\Cust_Details.json"           "$.phoneNumbers"             "PhoneNumbers"

End of the execution, the array data present under the phoneNumbers JSON key will be stored under the PhoneNumbers key. 

JSON.StoreAllUniqueKey

This action stores all the keys present in the JSON file. Multiple keys are stored separated by comma.

While executing this action, multiple instances of single key are counted as a single instance and it will be stored only once.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute path to the JSON file from which you want to get and store keys.

Yes

String

Key

Enter the key under which you want to store the JSON keys.

Yes

String

Example: 

JSON.StoreAllUniqueKey           "C:\Users\Qualitia\Cust_Details.json"           "AllKeys"

End of the execution, the complete list of JSON keys will be stored under the AllKeys key. Here AllKeys will store "firstName","lastName","age","address","streetAddress","city","postalCode","phoneNumbers","type","number".

JSON.StoreTotalKeyCount

This action stores the total number of keys available in the specified JSON file. The number is stored under the specified key.

While executing this action, multiple instances of single key are counted as a single instance and it will be counted only once.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute path to the JSON file from which you want to get and store total key count.

Yes

String

Key

Enter the key under which you want to store the JSON key count.

Yes

String

Example: 

JSON.StoreTotalKeyCount           "C:\Users\Qualitia\Cust_Details.json"           "TotalKeyCount"

End of the execution, the total number of keys will be stored under the TotalKeyCount (here, 10key.

JSON.StoreSpecificKeyCount

This action stores the total number of instances of specified JSON key available in JSON file. The number is stored under the specified key.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Types

FilePath

Enter the absolute path to the JSON file from which you want to get and store total number of instances of the specified key.

Yes

String

JSONKey

Enter the key name for which you want to store the count. 

Yes

String

Key

Enter the key under which you want to store the JSON key count. (case-sensitive)

Yes

String

Example: 

JSON.StoreSpecificKeyCount           "C:\Users\Qualitia\Cust_Details.json"           "TotalKeyCount"          "type"

End of the execution, the total number of instances of the key type will be stored under the variable TotalKeyCount. Here, number will be stored.

This action reads JSON file, navigates to the JSON path, and stores the value of the specified attribute in the key. The key value can be retrieved using the key name.

JSON.StoreValue

This action stores the value present under the attribute postalCode under the key PostalCode

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

JsonFilePath

Enter the absolute path to the JSON file from which you want to store the value.

Yes

String

Jsonpath

Enter the path to the node (J Path) from which you want to read and store the value.

Yes

String

strKey

Enter the key name under which you want to store the value.

Yes

String

Example: 

JSON.StoreValue    “C:\Users\Qualitia\Cust_Details.json”        “$.address.postalCode”         “PostalCode”

JSON.StoreJsonPathCount

This action stores the count of specified JSON node under the key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

jsonFilePath

Enter the absolute path to the JSON file in which you want to set the value.

Yes

String

Jsonpath

Enter the path to the node (J Path) to which you want to set the value.

Yes

String

value

Enter the value which you want to set against the specified attribute.

Yes

String

Example: 

JSON.StoreJsonPathCount     “C:\Users\Qualitia\Cust_Details.json”        “$.address.postalCode”         “630-0194”

This action will update the value of the attribute postalCode to the value given in the parameter (here 630-0194).

JSON.CompareJson

This action compares two JSON files and generates a comparison report in the HTML file.

The HTML report displays both the JSON files in the comparison view, highlighting the differences to easily identify the differences between selected two files.  

The report also displays the consolidated number of Missing properties, Incorrect values, Unequal values.

  • Missing properties: Gives the number of missing entities in one of the files.

  • Incorrect values: Gives the number of instances where JSON key is the same in both the files but value type is different.

  • Unequal values: Gives the number of instances where key and value type are same in both the files but value data is different.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

ActualJsonFilePath

Enter the absolute path to the JSON file path which you want to compare. 

Yes

String

ExpectedJsonFilePath

Enter the absolute path to the JSON file with which you want to compare the actual JSON file.

Yes

String

OutputHTMLFilePath

Enter the absolute path to the HTML file in which you want to store the comparison report.

Yes

String

MaintainSequence

Specify whether you want to consider sequence while comparing these two JSON files.

Set True to consider the sequence, else, set False to ignore the sequence while comparison.

Optional

String

Example:

JSON.CompareJson                         "D:\PatientDemographics.json"                    "D:\PatientDemo.json"                 "D:\PD_CompareReport.html"                     "True"

JSON.UpdateValueFromJson

This action reads a JSON file and updates the JSON key value as per the specified parameters and data type.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type 

FilePath

Enter the absolute file path to the JSON file where you want to add the node.

Yes

String

JSONPath

Enter the JSON path where you want to add the new node. 

Use $ if you want to add the node at root level.

Yes

String

JSONValue

Enter the value to be added for the JSONValue key.

Yes

String

JSONValueType

Specify the data type of the value being added.

Value type can be Boolean or Numeric.

Keep the value type blank if the data type is JSONObject, JSONArray, or String.

No 

String

Example:

  • Updating single value: 

.UpdateValueFromJson     “C:\Users\Qualitia\Cust_Details.json”        “$.address.postalCode”         “6300194”         “Numeric“

This action will update the value of the attribute postalCode of type Numeric to the value given in the parameter (6300194).

  • Updating value from the array: 

.UpdateValueFromJson    “C:\Users\Qualitia\Cust_Details.json”        “$[0].address.postalCode”         “6300194”         “ Numeric“

This action will update the value of the attribute postalCode of address at 0th index, type Numeric to the value given in the parameter (6300194).

  • Updating value of type String:

“C:\Users\Qualitia\Cust_Details.json”        “$.address”         “StateCode”        "["CA" , "California"]"        ""

End of the execution, this action adds a new node as state and value as CA and California under the node address.

JSON.UpdateValueInJson (Deprecated)

This action reads JSON file and updates the JSON key value as per the given parameter.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

jsonFilePath

Enter the absolute path to the JSON file where you want to set the value.

Yes

String

Jsonpath

Enter the path to the node (J Path) where you want to set the value.

If JSON path contains array, ensure you use an [] with index. Index starts from 0.

Yes

String

value

Enter the value which you want to set against the specified attribute.

Yes

String

Example: 

  • Updating single value: 

.UpdateValueInJson     “C:\Users\Qualitia\Cust_Details.json”        “$.address.postalCode”         “6300194”

This action will update the value of the attribute postalCode to the value given in the parameter (here, 6300194).

  • Updating value from the array: (see the example below)

.UpdateValueInJson    “C:\Users\Qualitia\Cust_Details.json”        “$[0].address.postalCode”         “6300194”

 View image

XML Actions

Qualitia Automation Studio contains the following actions to perform operations on the XML files.

  • XML.UpdateNodeValue

  • XML.StoreNodeValue

  • XML.StoreAttributeValue

  • XML.StoreNodeCount

  • XML.VerifyIfNodeExists

  • XML.VerifyIfAttributeExists

  • XML.UpdateAttributeValue

  • XML.StoreEvaluatedXPathResult

Also, you  can use ValidateStringSyntaxinFile to validates the syntax of an XML file.

XML.UpdateNodeValue

This action reads the specified XML file and updates the inner value of the specified node.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

XmlFilePath

Enter the absolute path to the XML file from which you want to update the value.

Yes

String

Xpath

Enter the path to the node (Xpath) whose value you want to update.

Yes

String

value

Enter the value which you want to add in the specified node.

Yes

String

Example: Web Services Actions#XMLExampleefer to the above image

XML.UpdateNodeValue         “C:\Users\Qualitia\Actors_List.xml”        "//actors/actor[@id='1']"         “Abraham Kennedy”

If you execute this action in the XML mentioned above, this John Doe will be replaced by Abraham Kennedy.

XML.StoreNodeValue

This action reads the specified XML file and stores the inner value of the specified node under the specified key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

XmlFilePath

Enter the absolute path to the XML file from which you want to get and store the value.

Yes

String

Xpath

Enter the path to the node (XPath) from which you want to read and store the inner text.

Yes

String

strKey

Enter the key name under which you want to store the node value (inner text from the node).

Yes

String

Example:

XML.StoreNodeValue         “C:\Users\Qualitia\Actors_List.xml”        "//actors/actor[@id="3"]"             “ActorName”

If you execute this action in the XML mentioned above, this William Kennedy will be stored under the key name ActorName. You can use the value stored under the ActorName key in the test case execution flow.

XML.StoreAttributeValue

This action reads the XML file and stores the value of the specified attribute under the key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key_Result

Enter the key name under which you want to store the attribute value.

Yes

String

XmlFilePath

Enter the absolute path to the XML file from which you want to get and store the value.

Yes

String

Xpath

Enter the path to the attribute (XPath) from which you want to read and store the value.

Yes

String

AttributeName

Enter the attribute name whose value you want to store.

Yes

String

Example: 

XML.StoreAttributeValue         “Key”        “C:\Users\Qualitia\Actors_List.xml”       "//actors/actor"            “id”

In this example above, as there are multiple nodes available under the specified xpath,  value of the first node will be stored under the specified key. 

XML.StoreNodeCount

This action reads the XML file and stores the count of the specified node under the key. The key value can be retrieved using the key name.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

Key_NodeCount

Enter the key name under which you want to store the node count.

Yes

String

XmlFilePath

Enter the absolute path to the XML file from which you want to get and store the node count.

Yes

String

Xpath

Enter the path to the node (XPath) from which you want to store the count. 

Yes

String

Example: 

XML.StoreNodeCount          “Key”        “C:\Users\Qualitia\Actors_List.xml”       "//actors"

In this example mentioned above, node count of the node actors will be stored in the specified key.

XML.VerifyIfNodeExists

This action reads the XML file and verifies whether the specified node exists in the XML document.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

XmlFilePath

Enter the absolute path to the XML file from which you want to get and store the existence of the node.

Yes

String

Xpath

Enter the path to the node (XPath) whose existence you want to verify. 

Yes

String

Existence

Value for this parameter can be either True or False.

  • Set True if you want to check the existence.

  • Set False if you want to check the non-existence.

Yes

String

Example: 

Xml.VerifyIfNodeExists           “C:\Users\Qualitia\Actors_List.xml”       "//actors/actor"             "True"

This action will verify whether the specified node exists in the XML file.

XML.VerifyIfAttributeExists

This action reads the XML file and verifies whether the specified attribute exists in the XML document.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

XmlFilePath

Enter the absolute path to the XML file from which you want to get and store the existence of the attribute.

Yes

String

Xpath

Enter the path to the attribute (XPath) whose existence you want to verify. 

Yes

String

AttributeName

Enter the attribute name whose existence you want to verify.

        Yes

String

Existence

Value for this parameter can be either True or False.

  • Set True if you want to check the existence.

  • Set False if you want to check the non-existence.

Yes

String

Example: 

Xml.VerifyIfAttributeExists                 “C:\Users\Qualitia\Actors_List.xml”         "//actors/actor[@id=1]"       "True"

This action will verify whether the specified ID attribute exists in the XML file.

XML.UpdateAttributeValue

This action reads the specified XML file and updates the inner value of the specified attribute.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

XmlFilePath

Enter the absolute path to the XML file in which you want to update the value.

Yes

String

Xpath

Enter the path to the attribute (Xpath) whose value you want to update.

Yes

String

AttributeName

Enter the attribute name whose value you want to update.

Yes

String

value

Enter the value which you want to add in the specified attribute.

Yes

String

Example: Web Services Actions#XMLExample

XML.UpdateAttributeValue         “C:\Users\Qualitia\Actors_List.xml”         "//actors/actor[@id=1]"            "id"              “4”

This action will update the attribute value of the specified attribute to the given value (here 4).

XML.StoreEvaluatedXPathResult

This action stores the result of the requested xpath under the specified key. The result can be anything including (but not limited to) inner value of the node and attribute and so forth. You must create request XML based on the required result.

The result stored under the key can be retrieved using key name.

(info) If the requested Xpath is returning multiple sets of values, Qualitia stores these values under key provided by user. Also, if there is no value to store under the key, Qualitia stores blank space.

Input Parameters:

Parameter Name

Parameter Description

Mandatory

Data Type

XmlFilePath

Enter the absolute path to the XML file from which you want to store the value.

Yes

String

Xpath

Enter the path to the attribute (Xpath) whose value you want to store.

Yes

String

Key

Enter the key name under which you want to store the result of the requested xpath.

Yes

String

Example: 

XML.StoreEvaluatedXPathResult         “C:\Users\Qualitia\Actors_List.xml”         "//actors/text()"            "Key"

Here, this action will store the empty space in the specified key, because there is no inner text present for the node <actors>.

XML.StoreEvaluatedXPathResult         “C:\Users\Qualitia\Actors_List.xml”         "//actors"            "Key"

Here, this action will return all the values from the actors node, including child nodes. In this example above, Qualitia stores John Doe Jane Doe William Kennedy inside the key.

{
  "firstName": "John",
  "lastName" : "doe",
  "age"      : 26,
  "address"  : {
    "streetAddress": "naist street",
    "city"         : "Nara",
    "postalCode"   : "6300192"
  },
  "phoneNumbers": [
    {
      "type"  : "iPhone",
      "number": "0123-4567-8888"
    },
    {
      "type"  : "home",
      "number": "0123-4567-8910"
    }
  ]
}

Deprecated Actions

Introduction 

You will find some actions listed in strikethrough text on the Test Cases and Tasks screens. We recommend not to use these actions when developing a new test case as there are better options available now for the same operation. While these actions will continue to work in this release, they might be taken away in future releases with appropriate migration methods.

In reports also, you will find these actions in the strike-through text.

Following is the complete list of deprecated actions:

AnswerForNextDialog

We recommend using the WaitForAlertAndSendText action instead of this action. In WaitForAlertAndSendText, Qualitia gives you provision to set and send the desired string in the next pop up being displayed. This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

ClickandchooseOkOnNextConfirmation

Instead of using this action, you can divide this into 2 steps for better maintenance and control;

  1. Click (based on the object class) and

  2. WaitForAlertAndSpecifyBehavior.

The WaitForAlertAndSpecifyBehavior allows you specifying the action to be taken on the next Alert Box as a first parameter (accept or dismiss). This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

ClickLinkAtCellandchooseOkOnConfirmation

Instead of using this action, you can divide this into 2 steps;

  1. ClickLinkAtCell and 

  2. WaitForAlertAndSpecifyBehavior.

The WaitForAlertAndSpecifyBehavior allows you specifying the action to be taken on the next pop up window as a first parameter (accept or dismiss). This action gives you more control by its ability to provide timeout and polling interval for the expected condition to be achieved.

StoreSubString

This action should be replaced with StoreSubStringNew. This new action does not have any change in the functionality but you will have better control and consistency during the test case execution. 

ClickAndWait

We strongly recommend not to use this action. Instead of using this action, we recommend you dividing it into 2 steps;

  1. Click and

  2. WaitForExistence or WaitForVisibility (based on the object class).

These actions give you more control by its ability to provide timeout and polling interval for the expected condition to be fulfilled.

You can also configure maximum wait time for the page to load using Page timeout (under Configuration Settings) or using the SetPageLoadTimeOut action

SelectItemAndWait

We strongly recommend not to use this action. Instead of using this action, we recommend you dividing it into 2 steps;

This action can be divided into 2 different steps for better performance and consistency:

  1. SelectItems and

  2. WaitForExistence or WaitForVisibility based on the next object you are going to operate on.

These actions give you more control by its ability to provide timeout and polling interval for the expected condition to be fulfilled.

WaitForPageToLoad

We strongly recommend not to use this action. Instead of using this action, we recommend using WaitForExistence or WaitForVisibility based on the next object you are going to operate on. Developing the test case this way gives you better control over your test case and help you find defects more effectively saving your time when debugging the test case. 

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.

WaitForObject

We strongly recommend not to use this action. Replace this action with WaitForExistence. Using WaitForExistence gives you better control over the test case resulting consistent test case execution.

Note:

  • For the WaitFor actions to complete successfully, the specified object must exist.

  • Only for all the Wait actions, you can override the actual execution result with that of your choice using the statusIfConditionNotSatisfied parameter. For example, if you set the statusIfConditionNotSatisfied parameter to Pass, the action execution result will always be Pass, irrespective of whether the actual execution result was Fail or Defect.



  • No labels