Page Comparison

Table of Contents

...

Expand

title	1. Gather or generate all java source files at one place.

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.

Launch command prompt.
Navigate to the %localappdata%\QualitiaWDClient\app-7.1.0\Dist folder.

Enter the following command:

“java -jar jd-cli.jar "<CLASS_FILE_SOURCE_PATH>" -od "<DESTINATION_FOLDER_TO_SAVE_SOURCE_CODE>"

Code Block

C:\Users\<HOSTNAME>\AppData\Local\QualitiaWDClient\app-7.1.0\Dist>java -jar jd-cli.jar "D:\ClassFiles" -od "D:\JavaFiles"
21:21:06.078 INFO  jd.cli.Main - Decompiling D:\ClassFiles
21:21:06.095 INFO  jd.core.output.DirOutput - Directory output will be initialized for path D:\JavaFiles
21:21:06.412 INFO  jd.core.output.DirOutput - Finished with 2 class file(s) and 1 resource file(s)

Post executing this command, source code files will be added at the destination folder. You can use them now to build and compile Eclipse project.

Expand

title	2. Create an Eclipse project and compile the project with all the custom actions.

To create and compile custom action project:

Launch Eclipse and create a new java project using an execution environment as JRE 1.8.
Set the bin folder as an output folder.
Add new folder and name it as lib.
The complete folder hierarchy will look something like this in the project directory.
Add all the existing custom action files in this directory.
Before you start adding custom action-related data into these sub folders, ensure that the code is working fine.
1. Add all the dependency files in the lib folder.
2. Add all the compiled class files in the bin folder.
3. Add all the java source files in the src folder.
  Ensure you add all your dependent jars in lib folder and provide the relative path for these jars in Build Path with the correct sequence.
Compile and build the Eclipse project.
Actions are now ready to be imported.

...

Expand

title	3. Import custom action code in Qualitia Project.

You can import the existing set of custom actions in Qualitia to share with the other project members easily.

Ensure the class files you are providing have all the custom actions functions present for which you have provided the metadata. A single class file can contain functions for multiple custom actions.

Log on to automation studio as a user with Manage Custom Action Code privileges.
Navigate to the project in which you want to import the custom action code and then click Develop > Custom Actions.
You will see the notification about importing custom actions on the top. This option is visible only if the project contains any custom actions that are not yet imported.
Click Import.
Provide path to the the Eclipse project which we have created and compiled earlier.
After importing all the custom action files successfully, click Close.
Eclipse project directory will be copied under Qualitia project path with all the sub-folders mentioned earlier (bin, lib, src, and so forth).
The Custom Action Repository Path under Configuration Settings will be set automatically to this new directory created under Qualitia Project Path.
In case there are any issues while importing the actions, these will be listed which can be exported in the HTML report.

Refer to the troubleshooting section to resolve the errors.

Info
In case you are using any version control system (Bitbucket or SVN), you need to push and commit this java project folder into the repository manually for the first time and all the Qualitia clients must pull the same on their respective systems. This is a one-time activity. Changes made to the custom actions thereon will be pushed automatically.

...

Creating a Custom Action for a Web/Mobile Project

Pre-Requisites

Eclipse IDE for Java Developers (Version 2019-03 recommended)
JDK version 1.8 and JRE version 1.8
Both JDK and JRE are bundled with the above Eclipse IDE version.
Custom Action Developer privileges in Qualitia
Set Eclipse Path under Project Settings
Add multiple jar files under Project Settings

Creating New Custom Actions

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:
1. 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.
2. 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.
1. To save the action, click Save.
2. 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.
1. To import the pre-created workspace, right-click Package Explorer, and select Import from the context-menu.
2. On the Import window, under the General section, select Existing Projects into Workspace and then click Next.
3. 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:
1. Add the dependent jar files in the lib folder under the project.
2. Right-click the Project, point to Build Path, and then select Configure Build Path.
3. Click Libraries > Add JARs.
4. Under Jar Selection window, expand the Project folder.
5. Under the lib folder, select the dependent Jar, and click Ok.
6. 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

...

Do in the following order listed to create necessary test artifacts:
1. Create a test case and include the custom action that you want to debug at the appropriate step. For more information, refer to Adding a Test Case Manually
2. From the test case editor, click Run to dry run the test case to verify whether the custom action is hit.
3. Create a test suite that contains the test case. For more information, refer to Creating a Suite.
4. Create an offline suite using the test suite. For detailed instructions, refer to Creating an Offline Package.
To add the required files for debugging the custom action:
1. Open the custom action you want to debug in the Eclipse project.
2. Add the TestHarness.Java file for the custom action in the Eclipse project.
3. Add the Config Folder in the Eclipse project.
4. In the config folder, open the startupSettings.json file, and specify the location of the offline suite for “SuitesDir”.
  For example: "SuitesDir":"D:/Qualitia Offline/Suite1"
Insert a breakpoint at an appropriate line number in the custom action.
Start debugging the TestHarness.Java file.
The test suite execution starts.
When the custom action is executed, the execution stops at the breakpoint you have inserted.
You can go ahead and debug the custom action.

...

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.

...

Expand

title	1. Gather or generate all java source files at one place.

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.

Launch command prompt.
Navigate to the %localappdata%\QualitiaWDClient\app-7.1.0\Dist folder.

Enter the following command:

“java -jar jd-cli.jar "<CLASS_FILE_SOURCE_PATH>" -od "<DESTINATION_FOLDER_TO_SAVE_SOURCE_CODE>"

Code Block

C:\Users\<HOSTNAME>\AppData\Local\QualitiaWDClient\app-7.1.0\Dist>java -jar jd-cli.jar "D:\ClassFiles" -od "D:\JavaFiles"
21:21:06.078 INFO  jd.cli.Main - Decompiling D:\ClassFiles
21:21:06.095 INFO  jd.core.output.DirOutput - Directory output will be initialized for path D:\JavaFiles
21:21:06.412 INFO  jd.core.output.DirOutput - Finished with 2 class file(s) and 1 resource file(s)

Post executing this command, source code files will be added at the destination folder. You can use them now to build and compile Eclipse project.

Expand

title	2. Create an Eclipse project and compile the project with all the custom actions.

To create and compile custom action project:

Launch Eclipse and create a new java project using an execution environment as JRE 1.8.
Set the bin folder as an output folder.
Add new folder and name it as lib.
The complete folder hierarchy will look something like this in the project directory.
Add all the existing custom action files in this directory.
Before you start adding custom action-related data into these sub folders, ensure that the code is working fine.
1. Add all the dependency files in the lib folder.
2. Add all the compiled class files in the bin folder.
3. Add all the java source files in the src folder.
  Ensure you add all your dependent jars in lib folder and provide the relative path for these jars in Build Path with the correct sequence.
Compile and build the Eclipse project.
Actions are now ready to be imported.

...

Expand

title	3. Import custom action code in Qualitia Project.

You can import the existing set of custom actions in Qualitia to share with the other project members easily.

Ensure the class files you are providing have all the custom actions functions present for which you have provided the metadata. A single class file can contain functions for multiple custom actions.

Log on to automation studio as a user with Manage Custom Action Code privileges.
Navigate to the project in which you want to import the custom action code and then click Develop > Custom Actions.
You will see the notification about importing custom actions on the top. This option is visible only if the project contains any custom actions that are not yet imported.
Click Import.
Provide path to the the Eclipse project which we have created and compiled earlier.
After importing all the custom action files successfully, click Close.
Eclipse project directory will be copied under Qualitia project path with all the sub-folders mentioned earlier (bin, lib, src, and so forth).
The Custom Action Repository Path under Configuration Settings will be set automatically to this new directory created under Qualitia Project Path.
In case there are any issues while importing the actions, these will be listed which can be exported in the HTML report.

Refer to the troubleshooting section to resolve the errors.

Info
In case you are using any version control system (Bitbucket or SVN), you need to push and commit this java project folder into the repository manually for the first time and all the Qualitia clients must pull the same on their respective systems. This is a one-time activity. Changes made to the custom actions thereon will be pushed automatically.

...

Creating a Custom Action for a Web/Mobile Project

Pre-Requisites

Eclipse IDE for Java Developers (Version 2019-03 recommended)
JDK version 1.8 and JRE version 1.8
Both JDK and JRE are bundled with the above Eclipse IDE version.
Custom Action Developer privileges in Qualitia
Set Eclipse Path under Project Settings
Add multiple jar files under Project Settings

Creating New Custom Actions

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:
1. 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.
2. 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.
1. To save the action, click Save.
2. 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.
1. To import the pre-created workspace, right-click Package Explorer, and select Import from the context-menu.
2. On the Import window, under the General section, select Existing Projects into Workspace and then click Next.
3. 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:
1. Add the dependent jar files in the lib folder under the project.
2. Right-click the Project, point to Build Path, and then select Configure Build Path.
3. Click Libraries > Add JARs.
4. Under Jar Selection window, expand the Project folder.
5. Under the lib folder, select the dependent Jar, and click Ok.
6. 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

...

Do in the following order listed to create necessary test artifacts:
1. Create a test case and include the custom action that you want to debug at the appropriate step. For more information, refer to Adding a Test Case Manually
2. From the test case editor, click Run to dry run the test case to verify whether the custom action is hit.
3. Create a test suite that contains the test case. For more information, refer to Creating a Suite.
4. Create an offline suite using the test suite. For detailed instructions, refer to Creating an Offline Package.
To add the required files for debugging the custom action:
1. Open the custom action you want to debug in the Eclipse project.
2. Add the TestHarness.Java file for the custom action in the Eclipse project.
3. Add the Config Folder in the Eclipse project.
4. In the config folder, open the startupSettings.json file, and specify the location of the offline suite for “SuitesDir”.
  For example: "SuitesDir":"D:/Qualitia Offline/Suite1"
Insert a breakpoint at an appropriate line number in the custom action.
Start debugging the TestHarness.Java file.
The test suite execution starts.
When the custom action is executed, the execution stops at the breakpoint you have inserted.
You can go ahead and debug the custom action.

...

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.

...

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.

...

Versions Compared

Old Version 8

New Version Current

Key

Creating a Custom Action for a Web/Mobile Project

Pre-Requisites

Creating New Custom Actions

Recommendations and Rules for Custom Actions

Creating a Custom Action for a Web/Mobile Project

Pre-Requisites

Creating New Custom Actions

Recommendations and Rules for Custom Actions