Search Results

This is the AIQ Web Designer. Web Designer allows the user to: Record a script by interacting with the AUT Edit existing text created by AISG or GENI Run and edit existing scripts (for example, using the "Record From Here" option to add missing steps,...

Last reviewed: September 30, 2026 Use this article when reviewing an AIQ web test execution and you need replay evidence to understand where a scenario failed. What changed in this article Clarified Instant Replay as a results-review and failure-analysis tool ...

Last reviewed: September 24, 2026 Use Edit and Play when a web testing step needs targeted JavaScript adjustment and immediate playback validation. What changed in this article Use small, reviewable JavaScript changes rather than replacing large scenario secti...

Recommended guidance Use SmartTag Workbench as a locator and object-identification reference when maintaining web tests. SmartTags should improve Scenario Editor stability by helping teams choose selectors that remain reliable across normal UI changes. What to...

Recommended guidance Use Network Workbench to understand network behavior that affects AIQ web testing, API validation, and troubleshooting. Network evidence should be reviewed alongside Scenario Editor steps, Output Logs, browser behavior, and application ser...

Last reviewed: September 30, 2026 Use this article to understand how Validation Workbench supports reusable validations for AIQ web testing workflows. What changed in this article Converted the page into a current overview of Validation Workbench purpose and v...

Last reviewed: October 2, 2026 Use this article when web tests need visual matching because a stable DOM locator, accessibility locator, or text locator is not available. What changed in this article Clarified visual accessors as a targeted fallback for web te...

Recommended guidance Use a Global JSON file when Scenario Editor tests need reusable configuration, environment values, or controlled data that should not be duplicated across many scenarios. Keep the file structured, reviewed, and version controlled. Good can...

Last reviewed: October 2, 2026 Use this article when a web test needs to compare generated or downloaded PDF output against an expected PDF or expected text content. What changed in this article Reframed PDF comparison around validation intent instead of gener...

Contents Mobile Designer - New User Interface Overview Mobile Designer (Classic) Mobile Testing Configurations Getting Started with Android and AIQ Getting Started with iOS and AIQ AWS Device Farm Mobile Testing Fallback Accessors for Mobile Testing Mobile Rec...

Legacy reference This page describes a Mobile Designer interface that should be considered legacy unless a customer is still maintaining older assets. Current guidance should use AIQ mobile testing and Scenario Editor terminology. Use this page for Migration c...

Legacy reference Mobile Designer Classic should be treated as legacy documentation. Keep this page only for teams maintaining older mobile testing assets. Current mobile testing guidance should use Scenario Editor and current AIQ mobile terminology. When this ...

Recommended guidance Mobile testing configuration should define the device, platform, application build, automation framework, network access, permissions, and evidence requirements before execution. Keep configurations explicit so failures can be reproduced. ...

Get Started with Android Testing in AIQ Use this checklist to prepare Android testing with AIQ. Exact device, emulator, and driver requirements can vary by AIQ release, so confirm the release-specific prerequisites before execution. Setup checklist Use a suppo...

Last reviewed: September 22, 2026 Use this page as a starting point for validating iOS workflows with AIQ mobile testing capabilities. Recommended guidance Confirm supported iOS versions, devices, simulators, and drivers for your AIQ version. Prepare certifica...

Recommended guidance Use AWS Device Farm when AIQ mobile testing needs coverage on real Android or iOS devices that are not available in the local lab. Treat Device Farm as an external execution environment: prepare the app build, test package, target device p...

Recommended guidance Fallback accessors help mobile tests continue to identify controls when the primary locator is unstable. Use them carefully: a fallback should target the same intended element, not merely a similar visible control. When to use fallbacks Mo...

Last reviewed: September 22, 2026 Use this article when beginning a mobile recording workflow for AIQ mobile testing. Recommended guidance Confirm the mobile device, app, and network are ready before recording. Keep recordings focused on a single business work...