Browser Versions for Scenario Editor Testing
Recommended guidance
Browser version alignment is important for reliable Scenario Editor playback. Validate the browser, browser driver, Test Node, operating system, and AIQ version together before treating a failure as a scenario defect.
When to check browser versions
- A scenario fails after Chrome, Firefox, Edge, or the operating system updates.
- Playback works on one Test Node but fails on another.
- Selectors, downloads, popups, certificates, or permissions behave differently between runs.
- Headless and headed execution produce different results.
Recommended checks
- Record the browser name, browser version, Test Node, operating system, and AIQ build used for the run.
- Confirm the browser is supported by the current AIQ release and the selected execution mode.
- Check enterprise-managed browser policies before changing browser settings.
- Reproduce with a controlled browser version when troubleshooting regressions.
- Update documentation and execution notes when a browser version becomes a known dependency.
Terminology note: Use Scenario Editor for current AIQ authoring and playback references. Older Test Designer references should be treated as legacy unless the page is specifically describing a legacy asset.
Last updated: October 5, 2026