This topic provides information on how to resolve the common issues you may encounter while working on web and mobile applications automation.

General Issues

This topic provides information about the general issues that you may see while working with Qualitia Studio.

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

Summary: This error occurs when the Selenium folder is missing in the Qualitia installation directory. This folder consists of all the browser drivers that are required for the test case executions using different browsers.

By default, this directory is created at the time of installation. The installation process may miss to create it in some specific environments.

Resolution:

Solution: Create a new folder in the Qualitia installation directory (%localappdata%\QualitiaWDClient), name it as selenium, and try launching Qualitia again.

Qualitia Shows Java Out of Memory Error

Problem: When launching Qualitia or dry running a test case or executing a test suite, Qualitia does not work and you see the following message:

java.lang.OutOfMemoryError: Direct buffer memory
    at java.nio.Bits.reserveMemory(Unknown Source) ~[?:1.8.0_231]
    at java.nio.DirectByteBuffer.<init>(Unknown Source) ~[?:1.8.0_231]
    at java.nio.ByteBuffer.allocateDirect(Unknown Source) ~[?:1.8.0_231]
    at io.undertow.server.DefaultByteBufferPool.allocate(DefaultByteBufferPo
ol.java:146)

Solution: You must install 64-bit Java on your computer with the latest patch for Java 8. Refer to Java website.

Exception Occurred While Launching Chrome. X Attempts Exhausted

This error occurs when the Google Chrome browser and Chromedriver are not compatible.
In such cases, you must update the browser driver versions. You can get the correct chrome drivers here.

Once downloaded, open Qualitia Automation Studio, go to Setting > Local Profile > Execution Configuration.
Click Browser > Chrome.
In Chrome Driver Path, select the chromedriver.exe which you have downloaded & extracted for your chrome version.
Click OK.

Your test cases should now get executed as expected.

Unable to Add Objects using Objects Spy

Suite Execution Fail Error: com.mysql.jdbc.Connection.isValid(I)Z

This error occurs due to incompatible driver version of MySQL. To resolve this error, you must download and place the compatible version of MySQL driver at the specified location.

To resolve this error:

Download the compatible version of MySQL Driver.
Unzip the file.
Copy mysql-connector-java-8.0.11.jar and place it to %localappdata%\QualitiaWDClient\app-5.x.x\WebDriver\lib location on the machine where you have installed Qualitia.
Navigate to %localappdata%\QualitiaWDClient\app-5.x.x\WebDriver.
Edit build.xml and replace mysql-connector-java-x.x.x-bin with the new file name (i.e. mysql-connector-java-8.0.11.jar).
Save and close the file.
Restart Qualitia Automation Studio.

Incompatible .Net Framework: Method not found: '!!0[] System.Array.Empty()'

Summary: This issue occurs when .Net framework you have installed is not compatible.

Qualitia Automation Studio requires minimum .Net Framework 4.6.2 installed on your system.

Solution:

Close the dialogue box and upgrade the .Net Framework to 4.6.2. Refer to the Prerequisites and Configurations section for more information.

To determine which .Net Framework version is installed, refer to the Microsoft documentation.

Error Messages in Qualitia Client Server Connection

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

Message	Description
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 the wrong password. The solution is to enter the correct password or request the admin to reset a password.
The Authentication has failed	When the user authentication fails due to an incorrect username.
No active session is mapped to the client	When 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.

Solution:

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

To resolve this error; create a new shortcut of Qualitia.

To create a new shortcut:

Remove an existing shortcut of Qualitia from Desktop.
Go to %localappdata%\QualitiaWDClient\app-4.1.0.
Right-click Qualitia.exe.
Click Send to and select Desktop (create shortcut).

User will get this error when executing test case for Desktop Web as well but Qualitia ignores this error and continues execution of test case.

Execute Tab and Database Restore Due to Less Packet Size

Problem: Upon clicking the Execute tab or when restoring Qualitia database, the following message is displayed: “throws error packets larger than max_allowed-packet are not allowed”.

Solution: Increase the max_allowed_packet size in the Database Server.

Qualitia Server is not Getting Connected

Problem: When clicking on the Test Connection button associated with the Qualitia Server URL in the Server Configuration tab, the following error message is displayed:

Cannot connect to the Qualitia Server, there might be the following reasons:
1. Port might not be accessible.
2. Server URL might be wrong.
3. Qualitia Server might not be running.

Summary: Qualitia Services might be unstable.

Solution: You need to repair the Qualitia services that are installed on the Qualitia server.

Perform the following steps:

Open the computer where the Qualitia Server is installed.
Double-click the Qualitia - Server icon on your desktop.
Click the Repair button.

Communication Fails when Qualitia Components are on Different Computers

Problem: If the Qualitia components (QAS client, QAS server, QAS database, QAS license server, and MOS) are on different computers, you may encounter the following error messages:

Execution is failing due to incorrect URL formation. Getting an error "Original error: Failed to connect to….” when executing a test suite.
Unable to connect to Qualitia server that is present on different machine than Qualitia client. Getting an error
Cannot connect to Qualitia Server there might be the following reasons:
1. Port might not be accessible.
2. Server URL might be wrong.
3. Qualitia Server might not be running.
Unable to connect to MOS server that is present on different machine than Qualitia client. Getting an error
Cannot connect to Qualitia MOS server there might be following error:
1. Port might not be accessible.
2. Server URL might be wrong.
Please ensure that MOS server is installed and the MOS service is running on the specified port.

Summary: This issue occurs if the Endpoint Security and VPN settings are restricting the communication between the components.

Solution: To resolve this issue you must enable communication between the Computers as follows:

All Computers must be connected over the same network.
Use VPN to connect all the Computer on same network.
Whitelist the following ports in the VPN.
- 4723 or the port number where the Appium server is running on the Macintosh Computer
- 21000
- 8887
- 8889
- 4001
Add rules to open TCP and UDP ports from the Endpoint Security Product.
Ensure that both the incoming and the outgoing traffic is allowed.
Ensure that you are connected to the VPN while creating rules using the Endpoint Security products.
Qualitia recommends using VPN generated IP address for secure communication. For example, to execute a test suite on a different Computer, you need to specify the IP address of that Computer in the execution profile.

You must refer to the documentation of your Endpoint Security product for instructions to allow communication between the Computers that contain the Qualitia components.

Licensing Issues

This topic provides information about the licensing issues that you may face while working with Qualitia Licenses.

Some organizations follow a practice of creating Virtual Machines (VM) with standard configurations and then clone it for different users to use. If they install Qualitia on the base image, Qualitia licensing manager may get duplicate installation id for the cloned VM. In all likelihood, the end user may receive a licensing error. It is, therefore, recommended to install Qualitia separately on the VMs after they are cloned.

When trying to log in to Qualitia, the user may get the following error [when the machine is cloned with Qualitia Installation].

Solution:

On the Qualitia License Server, open the url: http://localhost:1947/_int_/products.html
If you see following error “Disabled due to Cloning”, take the screenshot and open a support ticket.
If no such error is displayed in the Qualitia License Server, restart the “Sentinal LDK License Manager” service on the server system.
If the issue persists for a particular Qualitia Client system only, re-validate the settings documented here.

Solution:

This error occurs when the Sentinel License Manager is missing on the designated machine. Before initiating the Qualitia installation, you must first activate Qualitia license. Activating license includes installing Sentinel License Manager (haspdinst.exe).

To resolve this error:

Install Sentinel License Manager (haspdinst.exe).

You will find this file in the Support_Packages folder shared with Qualitia Automation Studio setup.

Sentinel HASP Run-time Installation

Sometimes, antivirus or firewall may block the Sentinel HASP. In order to continue the installation, please follow some steps mentioned below.

Solution:

Launch the Command Prompt as an administrator.
Navigate to the folder where haspdinst.exe exists.
Execute haspdinst.exe.
Continue the Installation Process.

Qualitia License Key Not Found. (H0007)

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 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 service using Windows services console.

If the issue still persists, follow the steps mentioned below:

Create a file with its name in the following format - hasp_108764.ini
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
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.
Open the url http://localhost:1947 and go to Configuration > Access to Remote License Manager, select all check boxes, add required information and then click Submit.
Go to Windows services console (Press Windows R and enter services.msc to open Windows Services console).
Select the service Sentinel LDK License Manager and restart it.
You should be able to launch Qualitia with license being acquired from the remote license manager.
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.

You can now log on to Qualitia Client without any error.

Test Data Issues

This topic provides information about the issues that you may face while working with test data.

Task Iterations Are 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 were executed.

Solution:

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

Perform the following steps:

Open the test case in which task iterations did not execute.
Open its Test Data explorer.
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.

Version Control Issues

This topic provides information about the issues that you may face while working with version control systems.

Unable to Push any Project Artifact to the Git Server

Problem: Unable to push any project artifact to the Git server.

Summary: The following error message is displayed while pushing the project artifacts to the Git repository on the Git command prompt window:

remote: “Repository not found”.

fatal repository ‘<gitserverurl>’ not found.

This error occurs when the Windows Credentials Manager on your computer has stored the old Git server credentials.

Solution:

Do one of the following:

If you have access to Manage Windows Credentials of your computer

Perform the following steps:

From the Start menu of your computer, open Control Panel.
Click User Accounts > Credential Manager > Manage Windows Credentials.
Delete all the credentials associated with the Git server.
After deleting the Git server credentials, push the project artifacts.

If you do not have access to Manage Windows Credentials of your computer

Perform the following steps:

Open the command prompt.
Enter the following command and hit Enter to delete the stored Git server credentials:
For /F "tokens=1,* delims= " %G in ('cmdkey /list ^| findstr git') do cmdkey /delete %H
After deleting the Git server credentials, push the project artifacts.

Filename too long (Git-version control system)

The older version of GIT has a restriction about file path. It does not accept the files that exceed the file path and name that has more than 256 or 260 characters.

To resolve this error, you can try following workarounds.

Workaround 1: Update the Git version to the latest one.
Workaround 2: Change Git settings by executing this command:
```
git config --system core.longpaths true
```

Workaround 3:
Update the registry key (in Windows 10, version 1607, and later)
HKLM\\SYSTEM\\CurrentControlSet\\Control\\FileSystem LongPathsEnabled (Type: REG_DWORD) should be set to 1.

If any of the workaround mentioned above does not work or you are unable to follow these workarounds due to any permission-related issues, you can move the Qualitia project to some local drive with relatively shorter path. Moving the project to the local drive or shorter path saves some character space and may resolve the issue.

Error in updating the test case, please check your access to GIT server. Git error: Too many redirects of error in authentication.

This error occurs when authentication details provided under Project Settings are incorrect.

To update Git/Bitbucket authentication details:

In Qualitia automation studio, go to Setting > Project Settings.
Update authentication details.
Click OK.
Restart Qualitia.

Version Control Error: Object Reference not set to an instance of an object.

This error occurs when SharpSVN is used as version control tool for the Qualitia test assets. Few SharpSVN components require Microsoft Visual C++ 2010 SP1 Redistributable package.

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

Error in Updating the test case, please check access to your SVN Server. SVN Error: None of the targets are working copies.

This error usually appears when the project artifacts (tasks, test cases) from the SVN server are not accessible from Qualitia client due to one or more reasons. This situation may occur when you update project folder names on either SVN server or on the local machine. While updating the project folder names, ensure you use the same folder names at both the locations; SVN Server and local machine (Project Path).

Also, these folder names are case-sensitive. This problem may appear if folder names are in different cases.

Object Spy Issues

This topic provides information that you may face while working with Object Spy.

Exception Occurred While Launching Chrome. X Attempts Exhausted

This error occurs when the Google Chrome browser and Chromedriver are not compatible.
In such cases, you must update the browser driver versions. You can get the correct chrome drivers here.

Once downloaded, open Qualitia Automation Studio, go to Setting > Local Profile > Execution Configuration.
Click Browser > Chrome.
In Chrome Driver Path, select the chromedriver.exe which you have downloaded & extracted for your chrome version.
Click OK.

Your test cases should now get executed as expected.

Unable to Add Objects using Objects Sp

Unable to Add Objects using Objects Spy on Google Chrome

Starting Qualitia Automation Studio v5.6, you can add objects using Object Spy for Google Chrome. In case you face any difficulties while adding objects using Google Chrome extension, uninstall the Qualitia Object Spy extension and reinstall it.

Object Spy Not Working

Qualitia Object Spy is an Internet Explorer (IE) plug-in embedded within IE window at the bottom of the page. It allows you adding objects in the repository while developing test cases or tasks. You can edit the objects in case of any changes to document structure and at the same time validate changes to objects.

In order to use this Object Spy tool seamlessly, user has to enable some options in Internet Explorer.

Go to Settings > F12 Developer Tools > Emulation > Mode > Document Mode.
Set Document Mode to Edge (Default), 8, 9, 10, or 11.

Sometimes, it has been observed that Object Spy does not allow users to add new or update existing set of objects. For "Object Spy in IE" this usually happens when Enable Protected Mode is ON and Internet security is set to High or Medium High. These options are found under Internet Options in the Internet Explorer.

Though we do not recommend this, however, an alternative can be to set the Enable protected mode ON and set the Internet security options to Medium. This but can have flaky behaviors here and there.

Qualitia Automation Web and Mobile Recorder Issues

Qualitia Automation Web Recorder is not Working

Problem: Qualitia Automation Web Recorder does not work and shows the following message "Recorder process could not be initiated within the stipulated time(120 s). Please try starting recording again".

Reason 1: AUT is not loading within 120s
Solution 1: You can check whether your application under test is taking more than 120 seconds to load. Contact Qualitia support on configuring the time-out.

Reason 2: This error message is displayed as your QAS client is using Open JDK.

Solution 2: Perform the following steps:

Go to the client installation location folder (%LocalAppData%\QualitiaWDClient\app-8.0.x) on your computer.
Open the Qualitia.exe.config file to set EngineDefaultMemory to -Xms512m, as follows:
<setting name="EngineDefaultMemory" serializeAs="String">
<value>-Xms512m</value>
</setting>
Save the file.
Restart the QAS client.

Unable to Switch to Mobile Web-View

Problem: In the Qualitia Mobile Recorder, you might not be able to open a web application or web-view context of a hybrid application if chrome has more than 20 open tabs. Unable to switch to Mobile Web View and Loader keeps on Loading the screen.

Solution: You are recommended to close all the tabs.

Problem in Viewing Samsung Galaxy S9+ in Qualitia Mobile Recorder

Problem: Samsung Galaxy S9 view + is distorted in Qualitia Mobile Recorder and MOS.

Solution:

Do the following in the order listed:

Go to the settings menu of Galaxy S9+.
Under Display the Screen Resolution, set to WQHD 1440x2560.

Unable to Start a Session on MOS or Mobile Recorder on Xcode version 11.6 or higher.

Problem: Unable to start session after selecting an application in MOS or Mobile recorder on Xcode version 11.6 or higher.

Summary: The WDA bundled along with the agent does not work on Xcode version 11.6 and higher.

Solution:

Perform the following steps:

Stop the agent.
Go to Applications > MOSAgent > Right click >Show package content > Contents > MacOS.
Double-click RunAgent.
A terminal opens to start the agent.
In the logs, find the following message using the WDA path:
/var/folders/vt/f2c8mcz536x6d9_vbgs7dh740000gn/T/QualitiaMOSAgent/WDATemp
Note: This path differs for every user.
Copy that path and open in finder.
Delete all the content inside the WDATemp folder.
Download WDA v2.20.0 for your Xcode version from the following location:
https://github.com/appium/WebDriverAgent/releases
Note: Download the WDA version that best matches to your Xcode Version.
Extract the downloaded file, copy all the contents, and paste
them in the WDATemp folder in the following location: /var/folders/vt/f2c8mcz536x6d9_vbgs7dh740000gn/T/QualitiaMOSAgent/WDATemp
Note: This path differs for every user, you must find the WDATemp folder path as explained in step. 4.
Open WebDriverAgent.xcodeproj in Xcode and make sure you set proper Team and check Automatically manage signing in the Signing and Capabilitiessection for WebDriverAgentLib, WebDriverAgentRunner and IntegrationApptargets.
Click Product > Build for >Testing.
After the build is succeeded, click Product > Build.
Close Xcode.
In the agent, connect to a device and select an application.
Note: You might have to perform this step every time you restart the machine as the temp folders are deleted and recreated whenever the machine restarts.

Unable to Boot Emulator in MOS Session.

Problem: The following error message "View For the device is failed. Please connect again" appears when you try to launch an emulator in an MOS Session is created with Cold Boot.

Reason: This error occurs when emulator (virtual device) is created using cold boot in Android Studio. There is some security issue when trying to read snapshot if we try to cold boot a device.. Currently, we do not support an emulator that is created using a cold boot.

Solution:
You need to select "Quick boot" as the boot action while creating the Android virtual device (emulator).

Perform the following steps:

Open Android Studio.
Click Tools > AVD Manager.
A pop up screen opens.
Click + Create Virtual Device.
Select the desired device you want, and click Next.
Select the desired API Level, and click Next
Note: If the API level is not downloaded, you need to download it.
Click Show Advanced Setting, and scroll down a bit.
From the Boot Option list, select Quick Boot.
Click Finish.

Browser and Devices Issues

This topic provides information about the issues that you may face while working with browsers and devices.

How to update Chrome Driver

You may face problems in test case executions in case the Google Chrome browser and chrome driver versions are not compatible. With new versions of google chrome browsers, it is important to update the chrome drivers to run the test cases flawlessly.

If the browser and driver versions are not compatible, you may get following error.

In such cases, you must update the browser driver versions. You can get the correct chrome drivers here.

Once downloaded, open Qualitia Automation Studio, go to Setting > Local Profile > Execution Configuration.
Click Browser > Chrome.
In Chrome Driver Path, select the chromedriver.exe which you have downloaded & extracted for your chrome version.
Click OK.

Your test cases should now get executed as expected.

Unable to Add Objects using Objects Spy on Google Chrome

Starting from Qualitia Automation Studio v5.6, you can add objects using Object Spy for Google Chrome. In case you face any difficulties while adding objects using Google Chrome extension, uninstall the Qualitia Object Spy extension and reinstall it.

Test Suite Execution Fails on Google Chrome Due to Certificate Authority

Problem: The test suite execution fails on Chrome with the following message "Certificate Authority. Invalid error".

Description: The certificate errors do not allow Qualitia to execute test suites.

Before executing the test suite, you need to configure the mapped or default execution profile from the Qualitia client.

If you are executing through the offline suite, open the Qualitia Offline Configuration Manager to select the offline suite and the mapped execution profile.

Perform the following steps:

Open the mapped or default execution profile.
Select the Browser as GoogleChrome.
Select the Edit Desired Capabilities checkbox,
Select the ChromeOptions checkbox.
Select the args checkbox, and enter the following text next to it: ignore-certificate-errors.

Now, re-execute the test suite.

This driver is not configured for integrated authentication

This error occurs when using Qualitia with SQL server 2016 developer edition and the Authentication Mode is set as Windows Authentication.

Solution:

Download Microsoft JDBC Driver 6.0 for SQL Server.
Unzip the file at some temporary location.
Go to enu > Auth.
Copy the dll depending on your OS (32 or 64-bit) version.
If you are using 32-bit, then copy sqljdbc_auth.dll from x86 folder and if you are using 64-bit, then copy sqljdbc_auth.dll from x64 folder.
Open the Java directory that is set under Settings>Configuration Settings.
Add the dll file to lib and bin folders.
If you are using jre7:
1. Go to enu > jre7.
2. Copy sqljdbc41 and add it to Qualitia installed location [C:\Program Files (x86)\Qualitia\Qualitia 3.14\WebDriver\lib].
If you are using jre8:
1. Go to enu > jre8.
2. Copy sqljdbc42 and add it to Qualitia installed location [C:\Program Files (x86)\Qualitia\Qualitia 3.14\WebDriver\lib.

Actions Issues

This topic provides information about the issues that you may face while working with actions.

DragAndDropToObject Action is not Working

Problem: The DragandDropToObject action fails to drag and drop an object to the specified location. The execution report displays the associated step as Passed though no operation was performed on the object.

Summary: The DragAndDropToObject action fails when the draggable attribute for the associated HTML element for the object is set to false.

Solution: Modify the associated HTML element for the object to set the draggable attribute to true or auto.

PressKeys Action Does not Execute on an Inactive Screen

Problem: The PressKeys action does not work when a test case is executed on an Inactive screen of a VM.

Summary: The test suite execution summary report shows the PressKeys action as Fail.

Solution: Perform the following steps:

On your local computer, close all open Remote Desktop sessions.
Launch the Registry editor (regedit.exe).
Do one of the following:
1. To specify the setting for the current user, open HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client.
2. To specify the setting for all the users, open HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client.
Create a DWORD value as RemoteDesktop_SuppressWhenMinimized and set it to 2 (hexadecimal or decimal).
Modify the registry settings on your local (controlling computer) so that minimizing the Remote Desktop window does not affect the GUI of the controlled computer.
Close the Registry Editor.

ClickJS Action is Failing on Chrome

Problem: ClickJS Action fails to execute on Chrome though javascript is enabled on Chrome. The application under test shows a message as Redirect Blocked.

A sample screenshot is shown below:

Solution: Before executing the test suite, you need to configure the mapped or default execution profile from the Qualitia client.

If you are executing through the offline suite, open the Qualitia Offline Configuration Manager to select the offline suite and the mapped execution profile.

Perform the following steps:

Open the mapped or default execution profile.
Select the Browser as GoogleChrome.
Select the Edit Desired Capabilities checkbox.
Select the ChromeOptions checkbox.
Select the args checkbox, and enter the following text next to it:
- --disable-web-security

Actions related to DB Failed Upon Execution

Problem: The actions related to querying on a database did not execute such as ExecuteQueryAndStoreInFile and ExecutQueryAndStoreInKey.

Description: For Quallita versions before v8.0.0, DB jar was manually added in lib folder. However, from Qualitia v8.0.x onwards, you now need to specify the path of DB jars for the database type on which you want to query.

Solution:

Perform the following steps:

Download one of the following relevant DB jar.
From the Qualitia client, select the associated project.
Click Settings > Project Configuration > Manage Dependent jar.
Enter the location of DB jar.
Click OK.

Now, execute the test suite again.

AttachFile Action Not Working/Failing

This action is designed to upload files from the local directory when executing the test case. In case your test execution environment is other than Local, such as Remote, Sauce, Perfecto, and so on, files will be uploaded from where you initiate the test case execution.
Also, execution of this action highly depends on the browser and driver version you are using.

For example: On Sauce Labs, this action found working seamlessly on Google Chrome version 60 and below and Mozilla Firefox version 47 and below with their default drivers. If the Google Chrome browser version is 61 to 64, you must use chromedriver version 2.29 for this action to work. This action does not work with Mozilla Firefox version 48 and above, Internet Explorer, and Safari browsers.

These findings are tested and verified at the time of documenting this information and are subject to change based on the changes made to the respective browser and driver versions.

Offline Package Issues

This topic provides information about the issues that you may face while working with an offline package.

Importing Offline Package Report

Description: Upon importing an offline package report, Qualitia sometimes might prompts the following error message: “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.

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

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:

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

iOS Platform and Macintosh Issues

This topic provides information about the issues that you may face while working on iOS Platform and Macintosh.

Test Case Execution on iOS platforms or a Macintosh Computer Fails

Problem: Test case execution on iOS platforms or a Macintosh computer fails with the following error:

“Execution is failing due to incorrect URL formation. Getting an error Original error: Failed to connect to /<VPN_ip_address_of_macintosh_computer>:<port>”

Summary: This issue occurs when the Endpoint Security Firewall settings on the Macintosh computer restricts communication from the Windows computer where the QAS client is installed.

Solution: To resolve this issue you must enable communication between the Computers as follows:

All Computers (in this case 2) should be connected over the same network.
Use VPN to connect all the Computer on same network
Whitelist the following ports in the VPN.
- 4723 or the port number where the Appium server is running on the Macintosh Computer
- 21000
- 8887
- 8889
- 4001
Add rules to open TCP and UDP ports from the Endpoint Security Product.
Ensure that both the incoming and the outgoing traffic is allowed.
Ensure that you are connected to the VPN while creating rules using the Endpoint Security products.
- Qualitia recommends using VPN generated IP address for secure communication. For example, to execute a test suite on a different Computer, specify the VPN generated IP address of that Computer in the execution profile.

You must refer to the documentation of your Endpoint Security product for instructions to allow communication between Windows and Macintosh Computers.

Unable to connect to MOS Server Running on a Macintosh Computer from the QAS client Running on a Windows Computer

Problem: Unable to connect to the MOS server on a Macintosh computer from the QAS client on a Windows computer. The following error occurs when you try to connect to the MOS agent on a Macintosh computer:
Unable to connect to MOS server that is present on different machine than Qualitia client. Getting an error
Cannot connect to Qualitia MOS server, there might be following reasons:

Port might not be accessible.
Server URL might be wrong.

Please ensure that MOS server is installed and the MOS service is running on the specified port.

Summary: This issue occurs when the Endpoint Security Firewall settings restrict communication from the Windows computer where the QAS client is installed.

Solution: To resolve this issue you must enable communication between the Computers as follows:

All Computers must be connected over the same network.
Use VPN to connect all the Computer on same network
Whitelist the following ports in the VPN.
- 4723 or the port number where the Appium server is running on the Macintosh Computer
- 21000
- 8887
- 8889
- 4001
Add rules to open TCP and UDP ports from the Endpoint Security Product.
Ensure that both the incoming and the outgoing traffic is allowed.
Ensure that you are connected to the VPN while creating rules using the Endpoint Security products.
Qualitia recommends using VPN generated IP address for secure communication. For example, To connect to the MOS server present on Macintosh Computer, specify the VPN generated IP address of the Computer on which MOS sever is running.

You must refer to the documentation of your Endpoint Security product for instructions to allow communication between Windows and Macintosh Computers.

Getting an issue in MOS session after Uninstalling the Older MOS agent and Installing a New MOS Agent due to WDA Dependencies on Macintosh Machine

Problem: When upgrading the MOS agent from any of its previous version, you may face issue in an ongoing MOS or Mobile Recorder session.

Reason: After uninstalling the previous MOS agent and MOS Server on the Macintosh machine, the WDATemp folder is not getting cleaned. Hence, when you install the new MOS agent build, it still uses the older WDA dependencies that are present in the WDATemp folder, which causes the problem.

Solution: After installing the new MOS agent on the Macintosh machine, you need to restart the machine. The WDATemp folder is cleaned and it downloads the newer WDA dependencies.

TFS/Azure DevOps Issues

This topic provides information about the issues that you may face while working with TFS/Azure DevOps.

Unable to Link Qualitia Test Cases with TFS/Azure DevOps Test Cases

Problem: Unable to link Qualitia Test Cases with TFS/Azure DevOps Test Cases.
Description: The message as “Error in linking the Test Case” is displayed. The reason is the user is missing certain access permissions in TFS/Azure DevOps.

Solution:

Qualitia integration with TFS/Azure DevOps expects that you have “Update Work Items” access that is used to generate the PAT (Personal Access Token).

The PAT with required access can be procured in one of the following ways:

Generate the PAT with a user that is part of the Project Administrators group.
Qualitia recommends this option for generating a PAT.
Allow Bypass Rules on Work Items Updates
Perform the following steps:
- In TFS/Azure DevOps project, ensure that the user that is used to generate PAT is member Contributors group / Project Team members group.
- Click Project Settings > Permissions.
- Select the user group that has the user to whom you want to provide access (Contributors/Project Team members).
- From the Bypass rules on work items updates list, select Allow.
  Refer to the following screenshot.

Qualitia does not recommend this option for PAT generation as it changes the access levels for all the users in the group.

Note: Please connect with your Azure DevOps Admin team to discuss the PAT generation and access level management.

Continuous Integration Issues

This topic provides information about the issues that you may face while working with Continous Integration tools such as Jenkins and Teamcity.

Unable to view Qualitia Suite Execution Summary Report in Jenkins

Problem: After an offline suite is executed using a Jenkins Job, the associated suite execution report is not displayed in Jenkins Reports.

Description: When you open the published suite execution report in Jenkins, you see any of the following behavior:

A blank page opens
The following message is displayed:
“You need to enable JavaScript to view this”

Solution:

You need to set up the content policy in Jenkins.

Perform the following steps:

Open the Jenkins Server.
Click Manage Jenkins >Manage Nodes.
Click the Settings icon for the node that you are using (Master node by default).
In the node page, select the Script Console option in the side menu.
In the script console, enter the following command line: System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "default-src 'self' 'unsafe-inline';")
Click the Run button below to this console, and you should see the Result: with the above values printed.
Note: If you don’t see it in the first attempt, then retry this step.
You can now see the suite execution summary reports.

Teamcity Agent Running Headless Execution on Window Server System

Sometimes users are unable to view the test case execution on the designated TeamCity build agent.

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

Install or upgrade Java to JRE 8.0 at the default location. (C:\Program Files\Java\jre1.8.0_101\bin\java.exe)
Update java path to this new location in the Environment Variables section (either under JAVA_HOME or Path).

Browser not supported