For the complete documentation index, see llms.txt. This page is also available as Markdown.

FAQs

How and where do I install the QloudBridge app?

You can download the installation files for the QloudBridge application from the Qyrus dashboard. For a step-by-step installation guide, please visit the QloudBridge Installation and Node Registration documentation.

What types of desktop applications can I test using the desktop testing service?

You can use the Desktop Testing service to test Windows and SAP applications.

How do I register my device as a node?

To register your device as a node, you should have the QloudBridge application installed on your machine. If it's not installed, please follow the steps outlined in the QloudBridge Installation and Node Registration documentation. After installation, follow the instructions provided in the same document under "Sign In to the QloudBridge App through the Windows Machine."

Can I run tests within the QB app?

Yes, after installing QB on your machine, you can select your respective teams, projects, modules, and test scripts. Once configured, the Run button will be available in the QB App for executing your test scripts.

Does QloudBridge need to be running throughout the Desktop Testing test execution?

Yes, QloudBridge should be running during the entire test execution process. Qyrus Cloud communicates with QloudBridge through the qyrus-connect tunnel to start the test and to stream execution progress and events back — if QloudBridge is closed or disconnected, the tunnel is terminated and any in-progress test will fail or lose event continuity.

Do I need administrator privileges to install or run QloudBridge?

No. With Qyrus Connect 2.0, QloudBridge runs entirely as a regular, logged-in user process. No "Run as Administrator" rights are required, and no Windows service or other system-level component is installed to establish the connection.

Do I need to open any inbound firewall ports for QloudBridge / Qyrus Connect to work?

No. Qyrus Connect only needs outbound connectivity. The qyrus-connect component embedded inside QloudBridge initiates an outbound, encrypted WebSocket (WSS) tunnel from your machine to Qyrus Cloud. Since the connection is always initiated from your side, you don't need to open, forward, or expose any inbound ports on your firewall or router.

What port does QloudBridge / Qyrus Connect work on?

Qyrus Connect only requires a single outbound port — 443 (HTTPS/WSS) — to reach Qyrus Cloud. No inbound ports are needed on your side. If your organization uses a corporate proxy or a TLS-inspection layer, make sure the Qyrus Gateway hostname is allowlisted/trusted for outbound traffic on port 443; check with your network administrator for the exact hostname to whitelist for your environment, since it is fetched automatically at connect time Qloudbridge creates an express server dynamically.

What will the payload sent for a test run contain?

When a desktop test is triggered, Qyrus Cloud sends a JSON payload through the qyrus-connect tunnel to the local QloudBridge service to start and run the test. At a high level, the payload contains:

Field
Description

run_id

Unique identifier for this test run

user_email

Email of the user who triggered the run

team_id / organization / organization_name

Identifiers for the team and organization the test belongs to

test_name / test_type / platform

Name of the test, its type (e.g. "Windows Testing"), and target platform (e.g. "WINDOWS")

is_suite_run / test_suite_uuid

Whether this run is part of a test suite, and the suite's identifier

test_scripts

Array of scripts to execute, each identified by script_name / script_uuid

steps

Ordered list of test steps within each script — each step defines the action (e.g. Launch, Attach To Window, Set, Kill EXE), the control_type / property / element details it targets, and the data_value needed to perform it

iterate_data

Present on loop-type steps — defines the iteration/exit conditions and the nested steps to repeat

eskm

Encrypted credential/secret material (e.g. stored passwords) needed for the run, always sent in encrypted form

continue_on_error

Whether execution should continue with subsequent steps if a step fails

visualregression_enabled

Whether visual regression checks are enabled for the run

A trimmed example of the payload structure looks like this:

Note: This is illustrative — actual payloads may include additional fields (such as nested iterate_data for loop steps, parameterization, and global variable references) depending on how the script was built.

Is Qyrus Connect a general-purpose tunnel to my internal network?

No. Qyrus Connect is scoped specifically to orchestrating QloudBridge desktop test execution and streaming runtime events back to Qyrus Cloud. It is not intended as a general-purpose tunnel for browsing or for accessing other internal applications on your network.

Can multiple users run QloudBridge on the same machine at the same time?

Yes. Qyrus Connect 2.0 fully supports multiple users on the same machine, including concurrent RDP/VM sessions. Each user's connection maintains its own independent tunnel and is fully isolated from other users' sessions.

Is QloudBridge / Qyrus Connect available on operating systems other than Windows?

The Qyrus Connect tunnel itself is cross-platform and runs on Windows, macOS, and Linux. However, the Desktop Testing execution engine (for running Windows and SAP application scripts) is only available on Windows. On macOS, after logging in to QloudBridge you will only see the Qyrus Connect option — Desktop Testing is not available there.

How can I find elements for desktop apps?

You can use our desktop application, QSpy, to locate elements for desktop apps. For detailed instructions, please refer to the QSpy and Recorder documentation.

Is it possible to record test steps?

Yes, Qyrus provides a recorder to capture test steps. For more information, please read the QSpy and Recorder documentation.

How do I delete a node?

To delete a node, navigate to the team-configuration page from the Qyrus dashboard. You will find your node listed there. Next to your node's name, there will be a red-colored "Delete" button. Click on it, and it will ask for confirmation. After confirmation, the node will be deleted.

How can I rename a node?

You can open the QloudBridge Application and, under the Node Registration section, update the Node Name.

How can I run tests on different teams?

To run tests on different teams, you need to delete your node from the previously registered team and then re-register it with the new team.

What should I do if I change my network connection?

With Qyrus Connect 2.0, you don't need to manually re-register your node when you switch networks. Simply click "Disconnect" and then "Connect" again on the Qyrus Connect page in QloudBridge — the connection parameters are re-fetched automatically and a fresh tunnel is established on the new network, VPN, or proxy. No manual IP address entry is required.

What happens to a running test if my network, proxy, or QloudBridge connection is interrupted?

Since Qyrus Cloud communicates with QloudBridge through the live outbound tunnel, any interruption to your network, proxy, or the QloudBridge process itself will break that tunnel. Active tests may fail or lose event/result streaming continuity until QloudBridge reconnects and the tunnel is re-established.

Can I import already created VB scripts?

Yes, you can import already created VB scripts. To learn how, please visit the Importing VB Script documentation.

Can I export steps created under Qyrus Desktop Testing and import them into another project?

Yes, you can export steps created in Qyrus Desktop Testing and import them into another project. For detailed instructions, please read the Import and Export Script documentation.

How can I manage test data for parameterized scripts?

You can manage your test data using our in-house solution, Test Data Management (TDM). To learn more about it, please refer to the TDM and Parameterization documentation.

Last updated