| Table of Contents |
|---|
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
...
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.
...
- 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:Port might not be accessible.
Server URL might be wrong.
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: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 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.
| Info |
|---|
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:
...
Does not Execute Test Case due to Add-Ons in Chrome
Problem: The following error message is displayed when executing a test case or a test suite:
Summary: This error occurs when due to certain organization security policies, Chrome disables the required Add-ons, which you can enable during the execution.
Solution:
To work around this issue:
Open the mapped or default execution profile.
Select the Browser as GoogleChrome.
Select the Edit Desired Capabilities checkbox.
Enter the following values:
Select the custom_use_chromeoptions checkbox.
Select the args checkbox, and enter the following text next to it:--disable-extentions.
Select the useAutomationExtension checkbox.
Click OK.
Now, re-execute the test suite or test case.
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:Port might not be accessible.
Server URL might be wrong.
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: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 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.
| Info |
|---|
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:
- 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.
- 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
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.
TCIteration
Selection
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.
...
Unable to Add Test Data
Problem: You may encounter any of the following pop-up messages while adding the test data:
Reason: The antivirus of your system has blocked the test data excel file.
Solution: Open the anti-virus of your system to whitelist the QAS Client setup folder that is located at the following location:
%localappdata%\QualitiaWDClient\app-8.2.XX
Also, ensure that files having extensions .dll, .exe, and .JAR files are not blocked.
If this issue still occurs, request the System Administrator to examine the anti-virus log file.
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:
|
If you do not have access to Manage Windows Credentials of your computer | Perform the following steps:
|
...
| Info |
|---|
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.
...
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.
...
...
Qualitia Object Spy does not add objects with XPath Locator Type
Problem: If a page contains more than 50 child elements, Chrome Qulaitia Object Spy may fail intermittently to add objects using XPath.
Summary: Chrome Qualitia Object Spy adds the object using a locator type other than XPath though you have specified XPath as the highest priority in the locator precedence.
Solution:
To work around this issue, increase the timeout from 1000 to 5000 in the pmr file.
- Navigate to the ChromeObjectSpyExtension folder.
- Open the pmr.json file.
- Under the "Configuration" object, set the timeout to 5000.
Unable to Add Object using Object Spy due to SQL Server Query Timeout
...
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.
...
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 toperform 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.
...
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.
Unable to Execute Test Cases on a Custom Browser Profile
Problem: Test case execution on a custom browser profile fails if any instance of the same browser is open. The error log of the test suite execution result contains the message “user data directory is already in use".
Root Cause: In the associated execution profile, the specified Capability Profile path is common for all the browser profiles.
Workaround: Close all the instances of the browser on which you want to execute the test case.
Test Suite Execution Fails on Google Chrome Due to Certificate Authority
...
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.
...
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.
...
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.
...
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:
...