Installing and Configuring Desktop Designer

Installing and Configuring Desktop Designer
Roku Environment Setup
Windows AIQ Driver Setup
Configure Open Broadcaster Software for AIQ Test Evidence
Set Up Roku Remote Control for AIQ Testing
Set Up Deep Link Tester for AIQ Mobile Testing
Arrange Applications for Reliable AIQ Desktop Testing
Troubleshoot Possible AIQ Performance Issues

Installing and Configuring Desktop Designer

Roku Environment Setup

Windows AIQ Driver Setup

Use this page when preparing a Windows machine to run AIQ browser, desktop, or device-related automation that depends on local drivers. Match driver versions to the target browser, operating system, and AIQ environment.

Preparation

Install drivers with an account that has the required Windows permissions.
Confirm the driver version matches the browser or application version used by the test.
Store drivers in a controlled path and document that path in the environment configuration.
Allow the driver through endpoint protection only when approved by IT or the customer security policy.
Restart related services or the machine when the driver installation requires it.

Validation workflow

Run a basic AIQ smoke test that starts the target browser or desktop application.
Confirm the driver process starts and stops cleanly.
Review output logs for path, permission, or version mismatch errors.
Record the driver version and installation path for future upgrades.

Last updated: October 8, 2026

Configure Open Broadcaster Software for AIQ Test Evidence

Open Broadcaster Software (OBS) can be used to capture video evidence while AIQ tests run. Use it when a team needs visual proof of application behavior, playback issues, or environment-specific failures.

Setup guidance

Install a supported OBS version on the machine where the browser, desktop app, or device stream is visible.
Create a dedicated scene for AIQ evidence capture and include only the required window, display, or device feed.
Set the output path to a location with enough disk space for the planned run duration.
Use a recording format that can be recovered if the session stops unexpectedly.
Mask or avoid capturing credentials, customer data, and unrelated desktop content.

Validation workflow

Start a short recording before the AIQ run.
Run a small scenario and confirm the video shows the relevant application state.
Check audio, resolution, timestamps, and file size.
Attach or reference the recording with the related execution evidence.

Last updated: October 8, 2026

Set Up Roku Remote Control for AIQ Testing

Use this guidance when AIQ tests need to control or validate a Roku-based application flow. Keep device setup consistent so remote-control actions are repeatable across test runs.

Setup checklist

Confirm the Roku device and test controller are on the required network and can reach each other.
Verify the app build, channel, or sideloaded package before running the scenario.
Use a dedicated test account and reset application state when needed.
Document the remote-control commands used by the scenario and the expected screen after each action.
Capture device logs or screenshots when troubleshooting navigation failures.

Validation workflow

Pair or configure the remote-control method for the target device.
Run a short navigation smoke test.
Confirm that AIQ can detect the expected screen or application response.
Record any network, pairing, or device-state requirements in the test notes.

Last updated: October 8, 2026

Set Up Deep Link Tester for AIQ Mobile Testing

Use a deep link tester when an AIQ mobile test needs to launch an app into a specific route, screen, or state. Deep links should be validated before they are added to repeatable mobile scenarios.

Prerequisites

Confirm the app build installed on the device or emulator supports the target scheme, universal link, or app link.
Document the exact deep link format, required parameters, and expected landing screen.
Use test accounts and non-production data when validating app navigation.
Reset the application state between runs when the deep link depends on login, cache, or stored preferences.

Validation workflow

Open the deep link manually on the target device and confirm the expected screen appears.
Add the deep link launch step to the AIQ mobile flow.
Run the test once with logging enabled and capture evidence.
Add assertions for the landing screen so failures are detected immediately.

Last updated: October 8, 2026

Arrange Applications for Reliable AIQ Desktop Testing

Arrange desktop applications consistently before an AIQ desktop test runs. Predictable window placement helps reduce failures caused by hidden controls, overlapping windows, or unexpected screen resolution changes.

Recommended setup

Use a dedicated test machine or session for desktop automation.
Set the display resolution and scaling before recording or running tests.
Open only the applications required by the scenario.
Place the application under test in a known position and avoid overlapping windows.
Disable pop-ups, notifications, and screen savers that can cover the application.

Validation workflow

Start from a clean desktop session.
Open the required application and arrange it as expected.
Run a short smoke test that validates the first interaction and a key screen state.
Capture a screenshot if the arrangement is part of the support procedure.

Last updated: October 8, 2026

Troubleshoot Possible AIQ Performance Issues

Use this article when AIQ feels slow, executions queue unexpectedly, reports load slowly, or test nodes are not keeping up with scheduled demand. Start with environment evidence before changing configuration.

Common areas to review

Host resources: CPU, memory, disk I/O, and available storage on controller, database, and test-node hosts.
Database health: Result-table growth, slow queries, retention settings, and backup activity.
Test-node capacity: Number of concurrent executions, browser/device availability, and node connectivity.
Scenario design: Excessive waits, unnecessary screenshots, large payloads, and missing cleanup steps.
Network path: Latency or firewall issues between AIQ services, test nodes, databases, and target applications.

Recommended workflow

Capture the exact symptom, affected time range, and AIQ components involved.
Review logs and resource metrics before restarting services.
Run a small known-good scenario to separate platform issues from scenario-specific issues.
Apply one change at a time and record the result.

Last updated: October 8, 2026