| Table of Contents | ||||
|---|---|---|---|---|
|
...
| Expand | ||
|---|---|---|
| ||
In order to import and streamline the custom actions with other project data in Qualitia, you must add all the java source files at one place. In case you do not have source files for some actions, you can generate the source code files easily using these commands mentioned below.
|
| Expand | ||
|---|---|---|
| ||
To create and compile custom action project:
|
| Expand | ||
|---|---|---|
| ||
You can import the existing set of custom actions in Qualitia to share with the other project members easily.
|
...
From the Expand Menu, click Develop.
Click the Custom Actions tab.
Click the Add Button (
) or Create Custom Action button.
The Custom Actions screen appears.Select Base Class.
The Custom Object Class file name including its file path should not exceed 256 characters when you are using Git/Bitbucket as a source control system for maintaining project artifacts.Do one of the following:
To add a new Qualitia Class:
Click the Plus button next to Custom Object Class to add a custom object class by mapping to the Qualitia Class that you want to add.
Enter the java class file name without its extension along with the package name (if required), in Qualitia Class.
To select a pre-defined Qualitia Class that is mapped to a Custom Object Class:
From the Custom Object Class drop-down list, select a pre-defined custom object class.
The associated Qualitia Class is selected automatically.Info title Points To Know - For example, if you add a Qualitia Class "com.security.login", then this file creates a package and a java file called as "com.security" and "login.java" respectively.
- The Custom Object Class is a user-friendly alternate name for a Qualitia Class, which you can specify.
Enter Action Name, Description and Function Name for the action to be created.
In the Properties section, click Add.
A new line will be added in the grid.Add Parameter Name, Description, ArgDataType for the parameter, and select whether this parameter is mandatory.
To save the action, click Save.
To save the action and launch the code template in Eclipse IDE, click Save and Launch Eclipse.
Close the Welcome on the IDE window to see your auto-generated custom action code template.
Import the pre-created Custom Action Java project workspace into Eclipse workspace.
This is a one-time activity for a project.To import the pre-created workspace, right-click Package Explorer, and select Import from the context-menu.
On the Import window, under the General section, select Existing Projects into Workspace and then click Next.
In the Select root directory section, click the Browse button, select <PROJECTNAME>_QASJavaproject and click Finish.
You will find this directory under Qualitia project path.
In Eclipse IDE, from the Window menu, select Preferences.
Select General > Workspace > Select Refresh using native hooks or polling.
Click Apply and Close.
Ensure you do not change the method signature and provide only the method body. Changing the signature in code may break your action in Qualitia.
In the editor, add the custom action code in the provided template for your custom action.
To add the dependent jars, do the following in the order listed:
Add the dependent jar files in the lib folder under the project.
Right-click the Project, point to Build Path, and then select Configure Build Path.
Click Libraries > Add JARs.
Under Jar Selection window, expand the Project folder.
Under the lib folder, select the dependent Jar, and click Ok.
Click Apply and Close.
Build the project and close the Eclipse IDE.
To work this custom action code in the Qualitia automation test cases, you must build the project successfully.
You can now use this newly created custom action while developing task and test cases in Qualitia.
Recommendations and Rules for Custom Actions
...
Validation Error | Resolution |
|---|---|
.classpath file is not present in your Eclipse project location | Ensure that the Eclipse project was built successfully after adding all required artifacts (lib, bin, src folders) to it. This will create a .classpath file. |
.class files are not present in your Eclipse project location | Collect the required compiled .class files and add them to the Eclipse project (under bin folder). Names of the required files is mentioned in the report. |
Jar files mentioned in .classpath in your Eclipse project location | Collect all the required jar files and add them to your Eclipse project directory (under lib folder). |
Java source files are not present in your Eclipse project location | You need to generate the source code from the compiled class files and add them into the src folder under Eclipse project directory. For more information on the creating the source files, refer to the Importing Existing Custom Actions Created in Previous Qualitia Versions section. |
Once you have fixed all the errors mentioned above, you can continue importing custom actions in Qualitia.
...
Open the desktop project where you want to create a custom action.
From the Expand Menu, click Custom Actions.
Click the Custom Actions tab.
Do the following in the order listed.
Enter the name of action, in Action Name.
Enter the role of the custom action, in Description.
From the Technology drop-down list, select the technology under which you want to create a custom action.
From the Base Class drop-down list, select a base class.
If you select a base class as General to create general actions, you get a pop-up to select Java or VB.
Do one of the following:To do coding in VB , select VB, and continue performing the actions as mentioned here.
To do coding in Java, select Java. The dialog box for creating general actions opens. For more information, refer to creating a custom action for web and mobile projects.
From the VBS File drop-down list, do one of the following:
Select an existing visual basic file.
Select Create New File to create a new visual basic file. Enter the name of the new VB file you want to create without including its extension.
From the Functions drop-down list, do one of the following:
Select an existing function.
You must ensure that you do not map a function created for a General Action to a Non General Action and vice versa. However, if you do so, you might see unexpected behaviour of your Custom Action.
Select Create New Function to create a new function. Enter the name of new function.
Under Properties, do one of the following:
If you have selected an existing function, the existing arguments are displayed. You need to select data type for existing parameters.
If you have selected a new function, add new parameters along with their data types.
Do one of the following;
Click Save to save the custom action in the selected VB script file.
Click Save and Launch Editor to save the custom action in the selected VB script file and then launch this file in the VB editor.
The custom action is added.
Click Edit Code to write codes to develop the custom action.
You need to consider the custom action rules.
Rules for Mapping Custom Actions
...
From the Expand Menu, click Develop.
Click the Custom Actions tab.
In the left pane, click the desired custom action which you want to update.
Custom action details will appear in the right pane.Click Edit.
Update Action Name, Description, Function Name, and parameters details based on the requirements.
Click Save and Launch Editor.
Info For desktop project custom action developed in VB, you cannot add or remove parameters from the mapped function for an unused cutsom action from Qualitia client. To work around this issue, launch the associated VBS file from Qualitia client, add or remove parameters for the mapped function, and remap the function to the custom action from Custom Action window.
...