Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Table of Contents
maxLevel2

Installation and Upgrade Process Issues

...

You may have to reboot the system to get the changes effective. After rebooting system, run the setup.exe again.

Incompatible Client Server Version

Image Removed

This next-generation installer handles all server and client related updates easily. Users are requested to apply updates whenever made available by team Qualitia to maintain server-client compatibility.

Solution:

If you face this error, please apply the latest update available for Qualitia Server.

Change Communication Port for Qualitia Server

By default, Qualitia Server is configured to use communication port 8889. In case this port is being used by some another application, you may change this communication port to any other available port. 

To change the communication port for Qualitia Server:

  1. Navigate to %localappdata%\QualitiaWDServer\app-5.2.0\Server.
  2. Open the application.properties file.
  3. Update value for server.port.
  4. Save and close the file.
  5. Restart the Qualitia Server service from the Services console and continue installation. 

Exception in UpgradeProjectDatabase : <Project_Name>: Too many connections.

This error occurs when the number of projects is more than 50. In order to proceed with the upgrade process, you must then increase the limit of maximum connections allowed in the MySQL database settings. By default, 151 is the maximum permitted number of simultaneous client connections.  

You can set this limit from where the MySQL server maintains system variables that configure its operation. System variables can be set at server startup using an option file.

Increasing Limit using Option File (Windows)

You can increase this max_connections limit Using Options File (sometimes called Configurations File).  

  1. Navigate to C:\ProgramData\MySQL\MySQL Server 5.7 on the machine where MySQL is installed.  
  2. Edit the my.ini file using any text editor.  
  3. Update the value for max_connections 
  4. Save and Close the file. 
  5. Restart MySQL service to get the changes affected.  

Image Removed

For other related information, refer to the MySQL documentation. 

Increasing Limit using Option File (Linux) 

If the MySQL is installed on the Linux machine, you will find my.cnf file in the MySQL installation directory. You can update the value for max_connections in my.cnf file using any text editor.  

For more information, refer to the MySQL documentation. 

Other Issues

...

Case Sensitive Issues in Project Name

Description: If in the source control system (GIT and SVN), the letters of a project name change their case, then Qualitia does not allow to open the project

Solution: You need to change the project name in source control that matches with the Project directory in such a way that the case of every letter of the displayed project matches.

Info

If you are using Qualitia version 7.2.4 or above, then a dialog box prompts which asks to change the case of Project name from the background. Unless you do not do, Qualitia does not work or not allow to open the project.


Incompatible Client Server Version

Image Added

This next-generation installer handles all server and client related updates easily. Users are requested to apply updates whenever made available by team Qualitia to maintain server-client compatibility.

Solution:

If you face this error, please apply the latest update available for Qualitia Server.

Change Communication Port for Qualitia Server

By default, Qualitia Server is configured to use communication port 8889. In case this port is being used by some another application, you may change this communication port to any other available port. 

To change the communication port for Qualitia Server:

  1. Navigate to %localappdata%\QualitiaWDServer\app-5.2.0\Server.
  2. Open the application.properties file.
  3. Update value for server.port.
  4. Save and close the file.
  5. Restart the Qualitia Server service from the Services console and continue installation. 

Exception in UpgradeProjectDatabase : <Project_Name>: Too many connections.

This error occurs when the number of projects is more than 50. In order to proceed with the upgrade process, you must then increase the limit of maximum connections allowed in the MySQL database settings. By default, 151 is the maximum permitted number of simultaneous client connections.  

You can set this limit from where the MySQL server maintains system variables that configure its operation. System variables can be set at server startup using an option file.

Increasing Limit using Option File (Windows)

You can increase this max_connections limit Using Options File (sometimes called Configurations File).  

  1. Navigate to C:\ProgramData\MySQL\MySQL Server 5.7 on the machine where MySQL is installed.  
  2. Edit the my.ini file using any text editor.  
  3. Update the value for max_connections.  
  4. Save and Close the file. 
  5. Restart MySQL service to get the changes affected.  

Image Added

For other related information, refer to the MySQL documentation

Increasing Limit using Option File (Linux) 

If the MySQL is installed on the Linux machine, you will find my.cnf file in the MySQL installation directory. You can update the value for max_connections in my.cnf file using any text editor.  

For more information, refer to the MySQL documentation. 

Other Issues

Unable to launch Qualitia Automation Studio.Could not find a part of the path 'C:\Users\<USERNAME>\AppData\Local\QualitiaWDClient\Selenium'.

...

  1. Once downloaded, open Qualitia Automation Studio, go to Setting > Configuration Setting and then click Platform.
  2. Select Browser Type as Google Chrome.
  3. In Chrome Driver Path, select the chromedriver.exe which you have downloaded & extracted for your chrome version.
  4. Click Click OK.

Your test cases should now get executed as expected. 

...

To resolve this error, you must install Microsoft Visual C++ 2010 SP1 Redistributable package.


Image Modified

Root Cause: java.lang.Exception: C:\Users\<Username>\AppData\Local\QualitiaWDClient/WebDriver\Config/android.properties file does not exist.

Solution:

This error occurs when Qualitia is launched using the incorrect shortcut and shortcut and user tries to execute the test case for Mobile web or native application.

...

Teamcity Agent Running Headless Execution on Window Server System

Qualitia seamlessly integrates with TeamCity, Bamboo, Jenkins continuous integration tools. Sometimes users are unable to view the test case execution on theecution on the designated TeamCity build agent. 

It is observed that setting the right Java path resolves this problem. You can try below:

...

Qualitia Configuration File does not exist, can you please save Qualitia Configuration.

Image Modified

This issue occurs when the configuration file is missing. The file is created when you save the configuration settings for the first time.

This issue may occur when creating offline package (from File > Offline Package) as well.

Solution:

  1. Log on to Qualitia Automation Studio.
  2. On the Setting menu, click Configuration Setting.
  3. Click OK.
  4. Now create an offline package from File > Offline Package.

...

Resetting Password for System Users.

For system users, Qualitia uses the password of the machine where Qualitia client is installed. This password would only be changed if the user updates machine / AD / LDAP password.

Qualitia License Key Not Found. (H0007)

Image Modified

Solution:

In case you come across this error:
  • Ensure that the license server is up and running.
  • Verify that the Sentinel LDK License Manager service Manager service is started on the Qualitia client machine. (To open Windows services console; press Windows R and then enter Services.msc) 
  • Restart the Sentinel LDK License Manager Manager service using Windows services console.
If the issue still persists, follow the steps mentioned below:
  1. Create a file with its name in the following format - hasp_108764.ini
  2. Open this file using notepad and add the following setting in it:
    SERVERADDR = IP address of the license manager system.
    Broadcastsearch=1 
    For Example: If your license manager system’s IP address is 192.168.1.1 then setting will be: SERVERADDR = 192.168.1.1
  3. For Windows 7 and later versions, copy the hasp_108764.ini file to the following location: %localAppData%/SafeNet Sentinel/Sentinel LDK/
    Note: If not present, manually create folders SafeNet Sentinel/Sentinel LDK.
  4. Open the url url http://localhost:1947 and  and go to Configuration > Access to Remote License Manager, select all check boxes, add required information and then click click Submit.
  5. Go to Windows services console (Press Windows R and enter services.msc to open Windows Services console). 
  6. Select the service service Sentinel LDK License Manager Manager and restart it.
    You should be able to launch Qualitia with license being acquired from the remote license manager.
  7. For Verification if the license has been recognized by the license server, open the Sentinel ACC portal (http://localhost:1947) and click session to view the licenses acquired by various systems.

...

Multiexcerpt include macro
nameAttachFile-Note
pageQFWM:General Web Actions

Failed to Connect JIRA. Verify Username/Password

Image Removed

If you are unable to connect to JIRA from Qualitia

Importing Offline Package Report

Description: Upon importing an offline package report, Qualitia sometimes might prompt an error message

that “Projectname_projectdb.tblsuite_summery does not exist”.

Solution: You need to navigate to any other tab such as Development or Execution and return to the Reports tab. If the problem persists, restart the Qualitia client.

Failed to Connect JIRA. Verify Username/Password

Image Added

If you are unable to connect to JIRA from Qualitia Automation Studio (Configuration Settings), try logging in manually using browser.

Atlassian applies CAPTCHA policy in case of failing login attempts due to user name or password mismatch.


Error Messages in Qualitia Client Server Connection

The following table shows the error message displayed on the screen or shown in the logs.

...

Client Server Connection


The following table shows the error message displayed on the screen or shown in the logs.


MessageDescription

User is Inactive

When the user is marked as inactive in the database. The solution is the user must be activated from the database. 

Invalid Password

When the user has entered a wrong password. The solution is to enter the correct password or request admin to reset a password.

The Authentication has failedWhen the user authentication fails due to incorrect username.
No active session is mapped to the clientWhen a user logins again, the user is not able to find any session.
Could not find a client with the specified client Id

When the client id is invalid. The solution is to provide the valid client Id must be provided from the configuration file.

Could not find a user with the specified user Id

When user Id is invalid. The solution is to enter the correct user Id.



Task Iteration Executions

Task Iterations Not Getting Executed

Problem: Some task iterations are skipped.

Summary: In task iterations, some iterations execute, but the remaining task iterations do not execute or none of them are executed.

Solution:

You need to delete the blank cells associated with task iterations.

Perform the following steps:

  1. Open the test case in which task iterations did not execute.

  2. Open its Test Data explorer.

  3. Select the blank cells of the following columns, and Press Delete from your keyboard.

    1. TCIteration

    2. Selection

    3. DataSetTag
      Note: All the cells can be deleted in a single go except for the first cell immediate below to DataSetTag. You need to delete this cell separately.