Create a Desktop Test in AIQ - Legacy Desktop Designer Flow

Use this page only when maintaining a desktop automation flow that still depends on Desktop Designer. For new test authoring, prefer the current AIQ workflow and Scenario Editor where the test can be supported without legacy Desktop Designer assumptions.

Before creating or updating the test

Confirm the Windows application, browser, driver, and operating system versions used by the test environment.
Run the desktop application with a dedicated test account and non-production data.
Document the startup state, window title, and any required permissions before recording or editing steps.
Use explicit waits and stable selectors instead of relying only on screen timing.

Recommended workflow

Prepare the desktop environment and open the application in the expected starting state.
Create or update the desktop test steps in the legacy flow.
Add validation after major actions so failures are visible in output logs.
Run a short smoke test before adding the test to a larger suite.
Record migration notes if the test should move to a current AIQ workflow later.

Legacy note: Desktop Designer references are kept for existing assets only and should not be used to start new documentation patterns.

Last updated: October 8, 2026