Common Issues
Installation and Upgrade Process Issues
How to Verify Digital Signature Manually?
Qualitia digitally signs all the executable files shared with Qualitia Setup or installable. In case system fails to verify this Digital signature, it is recommended to verify the signature using few simple steps before continuing the operation.
To verify the Digital Signature manually:
- Right-click Setup.exe and select Properties from the context-menu.
- In the Digital Signatures section, click Details.
- Ensure you see appropriate Signer Information as mentioned in the screenshot below:
This ensures that the setup.exe is safe to run in the environment.
In case you find Signer Information missing, inform Qualitia Support immediately and abort the execution of such files.
Installation Has Failed or The application Could not be started.
This error occurs when multiple installation processes get started or some Windows features are not enabled.
Sometimes, unzipping Setup.exe takes more than usual time due to the system specifications or some other technical problems. Users are requested to wait for some time once they double-clicked Setup.exe.
Solution:
If you face the error mentioned above, close the dialogue box.
Ensure you have Enabled .Net Framework under Windows Features.
You can confirm whether this feature is enabled using these simple steps mentioned below:
If the server machine has Windows Server OS, navigate to Server Manager > Right-click Features and select Add Features.
If the server machine has Windows 7 and above, navigate to Control Panel > Programs and Features > In the right pane, click Turn Windows features on or off.
You may have to reboot the system to get the changes effective. After rebooting system, run the setup.exe again.
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.
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
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:
- 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.
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).
- Navigate to C:\ProgramData\MySQL\MySQL Server 5.7 on the machine where MySQL is installed.
- Edit the my.ini file using any text editor.
- Update the value for max_connections.
- Save and Close the file.
- Restart MySQL service to get the changes affected.
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'.
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:
To resolve this error, create a new folder in the Qualitia installation directory (%localappdata%\QualitiaWDClient), name it as selenium, and try launching Qualitia again.
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.
Exception Occurred While Launching Chrome. X Attempts Exhausted.
This error occurs when the Google Chrome browser and Chromedriver are not compatible.
To resolve this error, kindly download the correct chrome driver as per the browser version from here.
- Once downloaded, open Qualitia Automation Studio, go to Setting > Configuration Setting and then click Platform.
- Select Browser Type as Google Chrome.
- In Chrome Driver Path, select the chromedriver.exe which you have downloaded for your chrome version.
Could not generate the license because: enforcement type is incompatible.
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.
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.
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 > Configuration Setting and then click Platform.
- Select Browser Type as Google 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.
TC Out of Sync (Reports)
This error usually occurs when the execution of suite is started but the corresponding test case is edited or being updated by one or other users.
In case you face this issue, you open the corresponding test case from the Develop section, click Save and continue execution from Suite or Scheduler.
If you are getting this error after test case execution using Qualitia Bot, you need to create the test case execution XMLs again.
To create test case execution XMLs again:
- Navigate to the Execute section.
- Select suite from which you want to execute test cases.
- Mark the test cases which you want to execute.
- Click Save As XML.
In case the issue persists, please connect to Qualitia Support.
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 Qualitia Configuration settings are incorrect.
To update Git/Bitbucket authentication details:
- In Qualitia automation studio, go to Setting > Configuration Setting > General.
- Update authentication details.
- Click OK.
- Restart Qualitia.
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.
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.
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.
To resolve this error; create a new shortcut of Qualitia.
To create 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.
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.
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 Configuration Settings > Execution > Java Install Path.
- Add the dll file to lib and bin folders.
- If you are using jre7:
- Go to enu > jre7.
- Copy sqljdbc41 and add it to Qualitia installed location [C:\Program Files (x86)\Qualitia\Qualitia 3.14\WebDriver\lib].
- If you are using jre8:
- Go to enu > jre8.
- Copy sqljdbc42 and add it to Qualitia installed location [C:\Program Files (x86)\Qualitia\Qualitia 3.14\WebDriver\lib].
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:
- 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).
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.
Unable to Select Project Using Project Drop Down
This issue occurs when .Net framework installed is not compatible.
Qualitia Automation Studio requires minimum .Net Framework 4.6.2 installed on the system where client is being installed.
Solution:
If are not able to select the projects from the drop down list, you must upgrade the .Net Framework to 4.6.2. Refer to the Prerequisites and Configurations section for more information.
Incompatible .Net Framework: Method not found: '!!0[] System.Array.Empty()'
This issue occurs when .Net framework installed is not compatible.
Qualitia Automation Studio requires minimum .Net Framework 4.6.2 installed on the system where client is being installed.
Solution:
If you face the error mentioned above, 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.
Cloning Machines with Qualitia Installation is Not Supported
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 into 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 persist for a particular Qualitia Client system only, re-validate the settings documented here.
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.
Android Chrome Version - Chrome Driver Compatibility Issue
You may come across following types of errors when the chrome driver and browser versions are not compatible.
Qualitia depends on the web drivers for mobile Web application testing. In case the chrome driver is not compatible with the browser version, it is recommended to update the driver as well as chrome browser to the latest version.
For more information about latest driver version and detailed change logs, click here.
Unable to Add or Update Objects using Object Spy
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.
Unable to Launch Object Spy
If your Object Spy is not getting launched:
- 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.
Also, you must ensure you have set few settings under registry.
This is required when Object spy requires some permissions to be accessed or launched for adding objects in the object repository.
- Press Win+R to launch the Run dialog box.
- Type regedit and press Enter.
- In Windows 7 and Windows Vista, click the Yes or Continue button or type the administrator's password.
- Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Fipsalgorithmpolicy registry.
- Set the value as 0 as mentioned in the screenshot below.
- Close Registry.
- Log on to Qualitia as an admin user.
- On the Users screen, select the user for whom you want to reset the password.
- Click Reset Password button.
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:
- 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.
How to work with HTML form element?
In order to perform action against the form element, Qualitia user need not select/switch control in WebDriver. Selection/switching of control in WebDriver is ONLY required for frames/iframes and browser windows.
Form can be identified using regular identifiers such as Name, ID, and other relevant locators.
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.
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
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.
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 a wrong password. The solution is to enter the correct password or request admin to reset a password. |
The Authentication has failed | When the user authentication fails due to 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. |
ClickJS Action is Failing on Chrome
Problem: Chrome fails the step containing the ClickJS Action to execute even it has enabled JavaScript. The application under test shows a message as Redirect Blocked.
Solution: Before executing the test suite, configure the required setting.
Pre-requisite: You can resolve this issue if your Chrome version is from 80 to 83.
Perform the following steps:
On the file explorer, open the following file from a notepad:
%localappdata%\Local\QualitiaWDClient\app-7.x.y\WebDriver\config\googlechromedc.propertiesUncomment the key custom_use_chromeoptions.
Set custom_use_chromeoptions=true.
Uncomment the key args that is present in the next line.
Set args=--disable-web-security
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:
|
Unable to Open Qualitia Client
Problem: Qualitia Client is not opening.
Description: It is displaying the following message "Unable to launch Qualitia Automation Studio.Object reference not set to an instance of an object."
Solution:
Perform the following steps:
Open the Folder explorer, navigate to %localappdata%> Qualitia > WD > Client > settings.
Rename the QualitiaClientsettings.json to QualitiaClientsettings_old.json.
Navigate to %localappdata%, and rename the Qualitia_Software folder to Qualitia_Software_old.
Launch Qualitia Client, fill up the configuration settings, and then login to Qualitia Client.
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.
Solution:
Perform the following steps:
Open the following file from a notepad:
%localappdata%\Local\QualitiaWDClient\app-7.x.y\WebDriver\config\googlechromedc.propertiesUncomment the key custom_use_chromeoptions.
Set custom_use_chromeoptions=true.
Uncomment the key args that is present in the next line.
Set args=ignore-certificate-errors.
Now re-execute the test suites.
Offline Suite Execution Fails on a Macintosh Machine
Problem: Offline package execution fails on a Macintosh machine and displays the following message:
"Failed to create WDA session:[WD Proxy] Error: timeout of 240000ms exceeded"
Solution: Restart your computer or restart the Appium server help to resolve this issue.
Perform the following steps:
Copy offline package and offline suite to mac machine
Update offline suite xml path in /Users/localadmin/Downloads/7.3.9_QDEV-21147/Qualitia Offline/config/qualitia.properties
Go to /Users/localadmin/Downloads/7.3.9_QDEV-21147/Qualitia Offline
Hit command java -jar qualitiaoffline-7.3.9.jar
Observe execution
Check appium logs.
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 Qualitia Database Server.
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 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:
- 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).
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 were executed.
Solution:
You need to delete the blank cells associated with 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.
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.
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