Versions Compared

Old Version 1

changes.mady.by.user ravi.chandran (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user ravi.chandran (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

  1. Download the compatible version of MySQL Driver.
  2. Unzip the file.
  3. 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.
  4. Navigate to %localappdata%\QualitiaWDClient\app-5.x.x\WebDriver.
  5. 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).
  6. Save and close the file.
  7. 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 License Key Not Found. (H0007)

Image Modified

Solution:

In case you come across this error:

...

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

Image Modified

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.

...

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.

...

  1. Stop the agent.

  2. Go to Applications > MOSAgent > Right click >Show package content > Contents > MacOS.

  3. Double-click RunAgent.
    A terminal opens to start the agent.

  4. 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.

  5. Copy that path and open in finder.

  6. Delete all the content inside the WDATemp folder.

  7. 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.

  8. 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.

  9. 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.

  10. Click Product > Build for >Testing.
  11. After the build is succeeded, click Product > Build.
  12. Close Xcode.
  13. 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. 

Browser and Devices Issues

...

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:

  1. Open Android Studio.

  2. Click Tools > AVD Manager.
    A pop up screen opens.

  3. Click + Create Virtual Device.

  4. Select the desired device you want, and click Next.

  5. Select the desired API Level, and click Next
    Note: If the API level is not downloaded, you need to download it.

  6. Click Show Advanced Setting, and scroll down a bit.

  7. From the Boot Option list, select Quick Boot.

  8. Click Finish.

Browser and Devices Issues

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

...

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

Image Modified

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:

  1. Log on to Qualitia Automation Studio.
  2. On the Setting menu, click Configuration Setting.
  3. Click OK.
  4. 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:

Not able to connect to Qualitia MOS server, there might be the following reason:

  1. Port might not be accessible

  2. Server URL might be wrong

  3. Qualitia Server might not be accessible

  4. Server URL might be wrong

  5. Qualitia Server might not be running

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

  1. be running

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.

...

  • 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:

...