You might get following errors while importing custom actions in Qualitia automation studio. You must fix these errors to complete the import procedure.

Import Custom Action Cannot be continue due to following errors;...

You will get this error in case the directory you have selected to import custom actions is missing one or more required sub-folders.

Resolution:

To resolve this error, ensure you have selected the right directory to import custom actions and the selected directory has all the sub-folders created in it.

Importing Incorrect Qualitia Java Project to the Workspace

If the following error message is displayed.

Solution:

When you Import the pre-created Custom Action Java project workspace into Eclipse workspace, select the correct Custom Action Java project.

Updating Qualitia Project Path

After you change the project path in Qualitia, you must re-import the java project from the new directory into the existing java workspace.

Re-importing this java project is mandatory. Else, the user will not be able to access updated custom actions.

This is a one-time activity.

To re-import the project:

Ensure you clone all the project data to the new directory.
This includes Test cases, Tasks, Custom actions, and Java project folders (which hold all the latest custom action code).
Remove the existing project from the workspace.
To import the cloned java project from the new directory, 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.
This is in the new directory where you have cloned the Qualitia project data.
Select General > Workspace > Select Refresh using native hooks or polling.
Click Apply and Close.

Other Validations

While importing custom actions code into automation studio, Qualitia validates certain things. In case some files or code is missing, Qualitia gives the list of issues to fix to continue importing custom actions.

Here is the complete list of validations and resolutions to be done.

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 into Qualitia section.

Once you have fixed all the errors mentioned above, you can continue importing custom actions in Qualitia.

Custom Action Class Files Not Pushed to Project Path GIT Repository

Problem: While editing or adding a custom action, if you encounter the following message:

“The method or operation is not implemented.”

This indicates the custom action class files are not pushed to Project path GIT Repository correcty.