Turn your manual testers into automation experts! Request a DemoStart testRigor Free

Setup for desktop app testing (Windows Apps Only)

This article contains instructions on how to set up desktop app testing for Windows desktop applications from testRigor cloud servers.

First and foremost, it’s important to have access to a desktop computer with the application you want to test already installed. Most users prefer a virtual machine (VM) from an external provider because it is always on; however, it is also possible to use a local Windows computer. The following step work for either one, but keep in mind that a local Windows computer must be accessible via a reliable internet connection.

1. Enable Remote Desktop (RDP) for Windows.

Enable Remote Desktop in Windows settings. To do this, head to Windows Settings -> System -> Remote Desktop and switch Enable Remote Desktop to On.

2. Create Suite in testRigor

Once Remote Desktop is enabled on the Windows device being used for testing your application, it’s important to set up the connection with testRigor by providing the IPv4 address. To do this, click the Windows (or Start) > Settings > Network & Internet > Hardware Properties. The computer’s IPv4 address should be visible there. Copy that address and go to https://app.testrigor.com/home (you’ll have to log in if you have not already done so). Below New Test Suite, select Windows Remote Desktop from the Type of Testing dropdown, paste the copied IPv4 address into the Address field in the New Test Suite and provide the necessary credentials for testRigor to access the device.

If the computer is behind a VPN or firewall, access will need to be granted via tunneling. See documentation here.

3. Setup Microsoft Windows Application Driver (recommended).

Configure secure access from the testRigor servers to the local Microsoft Windows Application Driver (WinAppDriver). You can do this with a firewall (ask support for a list of testRigor server addresses) or by tunneling. To set up tunneling, contact the testRigor’s support team. They will allocate a separate port number and help you set up the tunnel.

Download the latest stable release of Windows Application Driver installer (now this is WindowsApplicationDriver_1.2.1.msi) from the official homepage https://github.com/microsoft/WinAppDriver/releases/ and install it (administrator rights will be required).

Enable Developer Mode in Windows settings. To do this, head to Windows Settings -> Update & Security -> For Developers and enable Developer mode.

Run WinAppDriver.exe from the installation directory (e.g., C:\Program Files\Windows Application Driver\).If you want to change the listening address/port (http://127.0.0.1:4723 by default), you will need administrator rights to run it.

Specify a URL of the running WinAppDriver in the testRigor test suite settings. To do this, head to Settings -> Remote Desktop -> Windows Application Driver URL. For a configured tunneling it will look like http://tunnel.testrigor.com:XXXX, where XXXX is the port number from the tunneling configuration for the WinAppDriver.

Related Articles

How to Automate 2FA Login with TOTP using testRigor?

TOTPs or time-based OTPs are a popular way of performing 2-factor authentication. They add an extra layer of security to logins ...

Import test cases from XRay for execution with testRigor

To ensure good software testing, you need more than test management. You need to be able to integrate with other testing tools to ...
On our website, we utilize cookies to ensure that your browsing experience is tailored to your preferences and needs. By clicking "Accept," you agree to the use of all cookies. Learn more.
Cookie settings
Privacy Overview
This site utilizes cookies to enhance your browsing experience. Among these, essential cookies are stored on your browser as they are necessary for ...
Read more
Strictly Necessary CookiesAlways Enabled
Essential cookies are crucial for the proper functioning and security of the website.
Non-NecessaryEnabled
Cookies that are not essential for the website's functionality but are employed to gather additional data. You can choose to opt out by using this toggle switch. These cookies gather data for analytics and performance tracking purposes.
one_parallelization_public