Web Testing with AIQ

Recommended guidance

Use AIQ web testing to validate browser-based user journeys, application behavior, and regression coverage through Scenario Editor. Current documentation should use Scenario Editor terminology instead of older Designer wording unless describing legacy assets.

Core practices

• Design scenarios around stable business flows and clear assertions.
• Use reliable accessors, waits, test data, and environment controls.
• Validate browser versions, Test Node configuration, downloads, certificates, and permissions.
• Capture useful evidence through screenshots, Output Logs, and reports.

Maintenance workflow

1. Run smoke tests after application, browser, AIQ, or Test Node changes.
2. Review locator failures for real UI changes versus unstable selectors.
3. Keep duplicate legacy web-testing pages consolidated when possible.
4. Document known browser policies or environment dependencies.

Last updated: October 6, 2026