The advantage of using this Custom Action is that users can reduce the time taken in creating objects for SalesForce Lightning.

Pre-Requisites

1. Install Java Eclipse.

2. Define the Eclipse Path in Qualitia Configuration Settings.

Map Actions in Qualitia using Eclipse

To map actions in Qualitia using Eclipse

1. Select the project in which you want to map the action.

2. Go to Develop> Custom Actions.

3. Click Add to add a new Custom Action.

4. Select Base Class as WebGeneral.

5. Edit the Custom Object Class by entering the values in Custom Object Class and Qualitia Class as SFDC_Standard_Function.

6. Enter the value in Action Name, Description and Function Name as label_Based_standard_input_operation.

7. Add the following three parameters:

   1. LabelName along with ArgDataType as String and select the Mandatory checkbox.

   2. LabelValue along with ArgDataType as String and select the Mandatory checkbox.

   3. TypeOfOpeartion along with ArgDataType as String and select the Mandatory checkbox.

8. Click Save & Launch Eclipse to save these values and launch the Eclipse.

9. After the Eclipse launches, click Import Projects. The Import dialog box opens.

10. Under General folder, select Existing Projects into Workspace, and then click Next.

11. Select QAS Workspace from your Project Path, and then click Finish.

    Eclipse creates a class as SFDC_Standard_Function.

12. Copy your Java code and paste to that class. Action file will be provided through an email.

13. Create a class as WaitMethod in Eclipse, and paste your WaitMethod Java code.

14. Save and close Eclipse.

15. Go to Develop>Test Case, open a new test case.

16. Verify under Action drop-down whether it is displaying label_Based_standard_input_operation.

About label_Based_standard_input_operation Action

This action identifies the UI objects based on their label names. As long as the object is present on the screen and displayed, it will be identified irrespective of the DOM structure.
The action handles the following six different types of objects:

• Textbox

• TextArea

• Dropdown

• Lookup

• Radio Button

• Checkbox

Input Parameters:

The action can be used to cover the following scenarios:

• Filling the Data

• Verifying the Object Size

• Verifying the Mandatory Error Message

• Verifying the Object Value

• Verifying the Object Disability

• Storing the Object Value

Filling the Data

You can enter the values in an object. If there are multiple values to add in an object, such as multi-select values in a drop-down list, then separate values by @@ .

You have to specify as FillData in Parameter 3.

Example:

Verifying the Object Size

You can verify the size of the object by specifying the length. For example, whether the maximum the size of the text box is up to 20 characters.

You have to specify the object length as Text^20, in which Text denotes it as text box, and length as 20.

Also, specify as SizeValidations in Parameter 3.

Example:

Verifying Mandatory Error Message

You can verify when a mandatory object is not selected or entered a value in it, then whether an appropriate error message is displayed.

You have to specify in the error message in Parameter 2 and MandatoryValidations in Parameter 3.

Example:

Verifying the Object Value

You can verify whether the object value entered or selected is displayed or verify a default value.

You have to specify in Parameter 3 as DetailsVerification.

Example:

Verifying the Object Disability

You can verify whether an object is disabled or not. You have to specify as $disabled$ in Parameter 2 and MandatoryValidations in Parameter 3.

Example:

Storing the Object Value

You can store an object value displayed in run-time or store a default value.

You have to specify as Keytostore in Parameter 2 and $storeText$ in Parameter 3.

Example: