Legacy Selenium IDE Import Reference
Last reviewed: September 28, 2026
Use this article only when a team still needs to understand older Selenium IDE assets in relation to AIQ.
What changed in this article
- Marked Selenium IDE guidance as legacy because current AIQ work should prefer Scenario Editor, supported Selenium/TestNG flows, or maintained automation code.
- Removed the implication that Selenium IDE is a primary authoring workflow.
- Added checks for export format, browser compatibility, locator quality, and whether the script should be rebuilt in Scenario Editor instead.
Validation workflow
- Confirm whether the Selenium IDE artifact is still needed or can be rebuilt in Scenario Editor.
- Validate exported commands and locators before importing or translating them.
- Run a small playback and review failures caused by outdated Selenium IDE commands.
Review note: This page now positions Selenium IDE as migration/reference content, not recommended new automation authoring.
Last updated: September 28, 2026
If you have feedback on this topic, contact documentation@appvance.ai.