Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

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

Updating Qualitia Project Path

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

To reimport the project:

  1. 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).
  2. Remove the existing project from the workspace.
  3. To import the cloned java project from the new directory, right-click Package Explorer, and select Import from the context menu.
  4. On the Import window, under the General section, select Existing Projects into Workspace and then click Next.
  5. 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.
  6. Select General > Workspace > Select Refresh using native hooks or polling.
  7. Click Apply and Close.

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.

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 ErrorResolution
.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 locationCollect 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. 

  • No labels