Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this Page:

Table of Contents


All the SFDCEdit class actions work with objects, which are defined under the following SFDC components in their DOM structure:

  • Input
  • textarea
  • inputCurrency
  • inputEmaiinputEmail
  • inputNumber
  • inputPhone
  • inputRichText
  • inputText
  • inpuTextArea
  • inputURL
  • inputSecret

Note: InputSecret supports the SecureSet action too.

Click

This action clicks the specified object.

This action does not have any parameters.

Example:

Click

Clear

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

This action does not have any parameter.

Example:
Clear

MouseOver

This action hovers mouse over the specified object.

This action does not have any parameter. 

Example:

MouseOver


Set

This action sets the focus on the specified object.

This action does not have any parameter. 

Example:

SetFocus

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="

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"


VerifyEnability

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


Parameter Name

Parameter Description

Mandatory

Data Type

enability

Enter one of the following:

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

No

String


Example:

VerifyEnability      "True"

VerifyExistence

This action verifies the existence of the specified object. 

Input Parameters:


Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

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

Yes

String


Example:

VerifyExistence      "True"

VerifyPropertyValue

This action verifies the existence of the specified object. 

Input Parameters:


Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

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

Yes

String


Example:

VerifyPropertyValue      "True"

VerifyVisibility

This action verifies the visibility of the specified object. 

Input Parameters:


Parameter Name

Parameter Description

Mandatory

Data Type

existence

Enter one of the following:

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

No

String


Example:

VerifyVisibility                          "True"