Table of Contents |
---|
...
- Navigate to %localappdata%\QualitiaWDServer\app-5.2.0\Server.
- Open the application.properties file.
- Update value for server.port.
- Save and close the file.
- 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.
...
- 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.
...
To resolve this error, you must install Microsoft Visual C++ 2010 SP1 Redistributable package.
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 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 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.
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.
...
- Ensure you launch Object Spy from Qualitia (Develop > Objects > Spy.)
Also, - Launch the Internet Explorer browser.
IE zoom should be set at 100%. - Click the Tools button from the top right corner and select Internet Options.
Ensure that the Enable Protected Mode option is deselected and Security level is Medium for all the sections (i.e. Internet, Local Intranet, Trusted Sites, and Restricted Sites).
- Click OK.
- Click the Tools button from the top right corner and select Manage add-ons.
- Enable ObjectSpy and ObjectSpy Toolbar add-ons.
- Click Close.
...
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)
Solution:
...
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 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
Qualitia seamlessly integrates with TeamCity, Bamboo, Jenkins continuous integration tools. 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:
...
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.
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:
Navigate to the following path:
%Localappdata%\QualitiaWDClient\app7.3.8\WebDriver\config\Open the googlechromedc.properties file to set the values besides to the following properties:
custom_use_chromeoptions=true
Args=--disable-extentions
useAutomationExtension=false