Document toolboxDocument toolbox

A new version of Qualitia Automation Studio for Web and Mobile 7.2.x is now available. We highly recommend you upgrade. Find more details here.

Mapping Actions in Qualitia

Mapping Custom Action in Qualitia

After you develop custom actions and tested it using Eclipse, you can now map these actions into Qualitia to use them in the test cases and tasks.

To map the actions in Eclipse:

  1. Log on to the Qualitia and create a project.
  2. On Develop tab, select Objects.
  3. Click Custom.
  4. If the object is of an existing type, and only one action needs to be developed, on the left pane, select a particular object type.
  5. Right-click and select New Class.

 

Adding New Object Class

  • Select the base class as set in the Java source file (parent class of Keyword class).
  • Enter the object class name as the name of the Custom Keyword class name.
  • Enter the Qualitia Class name as the fully qualified class name (full package name). If the class is a default package then enter only the class Name. 
     

     
    5.  If the object is a completely new Qualitia class, on the left pane, selects the appropriate technology. Right click and select New Class. 
    Adding New Object Class
  • Enter the object class name as the name of the Custom Keyword class name.
  • Enter the Qualitia Class name as the fully qualified class name (full package name). If the class is a default package then enter only the class Name.
     

    6.  Create the object manually for this new Custom class.
    7.  Map the Keyword written for this object by selecting the created class.
    8.  Select New Custom Action.
     
    9.  Enter the Action Name as given in the Java class.
    10. Enter the Description and Function Name as given in the Java class.
    11. Add the parameters in the Properties window.
    a. Do not set the ObjectInfo parameter as given in the Java class. You only need to add the parameters in the same sequence as given in the Java class excluding the ObjectInfo Parameter.
    b. Select the argument data type as String or Array. If the argument data type is an Array then in the Java class the parameter type needs to be Object. For example, the action written in Java class is mapped in Qualitia. The parameter ObjectInfo type is not given in Qualitia.
     

     
    12. Using custom actions in Test Cases:
    a. On Develop > Test Cases select a WebEdit Object.
    All the actions for WebEdit including the new Custom Actions will be displayed in the list.
    b. Select the Custom Action.
    The parameters appear.
     

    c. If the object is totally a new Object that is not present in Qualitia, only then the new created actions will be shown in the list.
    13. The Custom Actions can now be debugged in Eclipse or executed in Qualitia.
    14. To debug the Custom Actions, save the Test Case written in Qualitia using the Save As XML option.

Configuring Custom Action Repository Path

After you have mapped custom actions, you must set the Custom Action Repository Path in the Configuration Settings. This is to point Qualitia to the custom action code while executing test cases.

Path to all the class or dependent jar files should be added into the Custom Action Repository Path under Configuration Settings.

While adding the path to class files, parent folder directory should be added, whereas, an absolute path should be given if you have custom action code into the jar file or your custom action requires any jar file to get executed.

Multiple paths should be separated by a semicolon (;) and last file path should end with semicolon sign (;).

The custom action path may look something like:

Not finding what you need?