QualityMate does not execute successfully when the PC is locked or the remote connection is closed
Some QualityMate interactions depend on an active user session; otherwise, some calls could not be performed, producing unexpected results, for example the following error messages on the log file:
<exception message="The screenshot could not be obtained. Please validate the GUI is available in the current session.">
...
<exception message="The handle is invalid.">
Could not send mouse input. ErrorCode: 5
Could not send mouse input. ErrorCode: 5
Answer: The Windows SO needs some configuration in specific environments, there are explained in the following article: .
QualityMate is not recording a video of the full screen
Before version 8.14.1 QualityMate requires the installed to record the screen.
Answer: Check your Windows Display configuration on Scale and layout option is set with 100%. If this value is greater or less than that, the video won't record the full screen. Follow this to check your current scale and how to change it.
Desktop
My app flicks on the taskbar and doesn't gain focus (Desktop)
The windows notification area ShellExperienceHost.exe -ServerName:App.AppXtk181tbxbce2qsex02s8tw7hfxa9xb3t.mca was introduced in later versions of Windows OS to manage user notifications from apps. This app only runs when the notification area is open and suspends when it's closed. If this app is open or runs even when it's shut, it interferes with QualityMate automation preventing it from gaining focus.
Answer: The user notification area should be closed to ensure the correct functionality. If this app doesn't suspend itself, kill the process using the task manager. Multiple reiterations could require disabling Windows notifications and/or sending a click to the control before doing other interactions.
QualityMate is sending wrong keys when running on another PC
Quality Mate uses the OS keyboard layout to simulate keyboard key typing in the target app. Using special keys or key combinations depends directly on the keyboard language configuration and the current layout as the OS interprets them.
Answer: The environments that will use QualityMate should have the same keyboard layout configuration to prevent unexpected results from specific keys.
Web
QualityMate doesn't open a browser instance when doing an interaction
QualityMate depends on a web driver to execute the UI scripts in the selected browser.
The web browser opens and closes but doesn't execute anything
The behavior happens when the web driver version doesn't match the web browser's major version.
The webdriver has a different name, and QualityMate can't find it
Selenium looks for the driver's name (i.e., chromedriver.exe, IEDriverServer.exe), but some Nugets change it to specify if the driver is for x32 or x64.
Answer: If the method you are using to get the web driver is changing the name of the .exe, you can use the following lines in the .csproj project to rename it. Here is an example of the Internet Explorer web driver.
QualityMate throws expected browser binary location, but unable to find binary in default location
This error is thrown when the browser you are using was not correctly installed it. Even if you have the browser in its default directory.
Test that uses web browser doesn't open and throws a FileLoadException after v8.16.8
This error is produced when the Microsoft.NET.Test.Sdk NuGet is not added in the project, creating an unexpected exception when launching certain browsers.
Answer: By default, this NuGet is added on test projects. If the package is missing, add the Microsoft.NET.Test.Sdk NuGet in the test project. Make sure that the following NuGets are added in your test project:
Microsoft.NET.Test.Sdk
MSTest.TestAdapter
MSTest.TestFramework
Internet Explorer
QualityMate gets stuck in web driver URL when Internet Explorer is running in private mode
After running a test, the web driver stuck in a localhost webdriver page and didn't use the Application parameter.
Internet explorer runs extremely slow and throws timeout exception
After running a test, the internet explorer automatization goes slow, performing clicks and SendKeys with a noticeable delay and throwing a timeout exception.
Answer: The IEDriver should match the Internet Explorer architecture to work without issues. If the driver does not match the architecture, you will need to download another driver with the corresponding architecture or change the Internet Explorer architecture using the Windows Registry by editing the key HKLM_CURRENT_USER\\Software\\Microsoft\\Internet Explorer\\Main\\TabProcGrowth assigning the value to 1 (32 bits) or 0 (64 bits)
Answer: Install the corresponding driver for the used web browser. If you don't know which one install, follow this article: .
Answer: Check if the web driver's major version matches your browser's major version, following this article: .
Answer: There are two options to solve this issue, the first is checking that the browser is part of the environment variables. If you don't want to do that, you can also use the and define your browser location.
Answer: Internet Explorer needs a special configuration to use the driver; also, it's necessary to use the x64bits IEDriver; these are explained in the following article: .