In order to create the custom actions for Selenium Webdriver, you need to create the action in Java and then map this action into Qualitia Automation Studio. You can use any IDE tool like Eclipse.
The following are some rules that should be considered when creating custom actions:
- The parameter data types supported by Qualitia are String and Array. If an array parameter is used in Qualitia for the custom action, then the custom action parameter should be of the type Object in Custom Action function. The parameter can then be type-casted into the data type which is required in the action.
For example, the object parameter can be type-casted into the array list. - All custom actions must return following integer values only.
- If action gets passed, return value should be 0.
- If action gets failed, return value should be 1.
- If action has defect, return value should be 2.
- No two custom actions can have the same function name in the same class. Function overloading is not allowed. Duplicate function names in different classes are allowed.
- No two custom actions can be in the same package hierarchy. Such instances may occur when multiple custom actions with the same name are created in different Java projects using same package hierarchy.
- Any new custom object created in Qualitia cannot be imported. You must create the object manually and map it to the relevant custom class in Qualitia.
- Once the action is mapped into Qualitia and used in a test case, do not change the existing signature or other details of the actions or the classes created. The functionality of the action can be modified. Do not delete the custom actions or custom classes that are used in test cases.
