2.4 - Desktop Designer

Desktop Designer — Appvance IQ documentation.

Desktop Testing with AIQ - Legacy Desktop Designer Reference
Desktop Designer User Interface Overview - Legacy Reference
Create a Desktop Test in AIQ - Legacy Desktop Designer Flow
Kindle Desktop App Example - Legacy AIQ Desktop Test

Desktop Testing with AIQ - Legacy Desktop Designer Reference

This page is retained as a legacy reference for teams that still maintain Desktop Designer assets. For current AIQ authoring, prefer Scenario Editor and the supported desktop testing workflow for the target environment.

When to use this reference

Use it only when maintaining an existing Desktop Designer test or troubleshooting an older desktop automation flow.
For new work, create or migrate tests through the current AIQ workflow instead of starting new Desktop Designer-only content.
Confirm operating system, driver, browser, and desktop application versions before rerunning older scripts.

Maintenance guidance

Review whether the legacy script is still required.
Update selectors, waits, and environment assumptions before execution.
Run the test in a controlled environment and capture evidence for any failing step.
Document migration candidates so duplicate legacy content can be retired later.

Obsolete-content note: The old Desktop Designer terminology is legacy. Keep references only where they explain existing assets that have not yet moved to the current AIQ workflow.

Last updated: October 8, 2026

Desktop Designer User Interface Overview - Legacy Reference

This overview is preserved for users who maintain existing Desktop Designer assets. Current AIQ documentation should use current product terminology and avoid treating Desktop Designer as the default authoring experience.

How to use this page

Use it to identify legacy Desktop Designer controls when troubleshooting an older desktop test.
Do not use it as the source of truth for current Scenario Editor or Service Suite workflows.
Confirm whether a legacy action has a current AIQ equivalent before updating related documentation.
Capture screenshots only when they reflect the currently supported version of the UI.

Review guidance

Check whether the linked desktop test still exists and is still needed.
Update outdated control names only when they are visible in the current environment.
Flag screenshots or UI labels that no longer match the product.
Move reusable guidance into the current AIQ workflow when possible.

Legacy note: This page should remain clearly labeled as legacy until the older Desktop Designer content is consolidated or retired.

Last updated: October 8, 2026

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

Kindle Desktop App Example - Legacy AIQ Desktop Test

This example is retained for teams that still reference older Desktop Designer desktop automation patterns. Treat it as a legacy sample, not as the preferred pattern for new AIQ authoring.

What this example demonstrates

Starting a desktop application from a known state.
Interacting with application windows and controls that may change across versions.
Adding validation after navigation or content-loading steps.
Capturing evidence when the app, driver, or operating system behavior changes.

Maintenance guidance

Confirm the Kindle application version and the Windows environment before rerunning the sample.
Replace brittle image-only steps with more stable selectors or validations where possible.
Use test data that does not expose personal account content.
Run the sample as a smoke test before using it as a template for another desktop application.

Obsolete-content note: Keep this page only as a legacy example. New examples should use the current AIQ workflow and current terminology.

Last updated: October 8, 2026