Selenium

• Selenium Integration Reference for AIQ
• Features and Benefits of Selenium
• Repurposing Methodology and Architecture for AIQ Integrations
• Test Workshop Tutorial
• Data-Driven Test Development in AIQ
• Legacy Selenium IDE Import Reference
• Review Selenium Commands and Results in AIQ
• Maintain TestNG Framework Scripts in AIQ
• Selenium Integration FAQ for AIQ

Selenium Integration Reference for AIQ

Last reviewed: October 2, 2026

Use this article as a high-level reference for maintaining Selenium-based assets that still interact with AIQ workflows.

What changed in this article

• Converted the generic Selenium page into a scoped AIQ integration reference.
• Added guidance to treat Selenium assets as maintained dependencies with browser driver, framework, data, and reporting checks.
• Added migration guidance for when Selenium coverage should be replaced by Scenario Editor or other AIQ-native workflows.

Validation workflow

1. Confirm what Selenium asset is being integrated and who owns its maintenance.
2. Validate browser/driver compatibility, framework dependencies, test data, and result handoff into AIQ.
3. Document whether the Selenium asset will be maintained, migrated, or retired.

Review note: This article now avoids presenting Selenium as a blank standalone topic.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Features and Benefits of Selenium

AIQ integrates Selenium to provide the following features and benefits:

• AIQ re-purposes a single Selenium test as a functional test, load test, and performance test.

• Scale up your Selenium tests to operate in your QA lab, in the Appvance On-demand Cloud Test Environment, or both!

• AIQ data-enables Selenium tests for test-driven development.

• Dramatically reduce test operating costs. AIQ efficiently operates multiple Selenium tests in a grid concurrently.

• AIQ runs Selenium tests for browser compatibility testing of your Web application.

• Produce actionable knowledge by analyzing the results into 350 or more performance and functional charts.

• Transform Selenium tests into Java unit tests for additional features: looping, variables, conditionals

• Run At User Levels Never Before Possible - Building a test lab used to be prohibitively costly for medium and large-scale load tests. Cloud computing delivers bandwidth and computing power to achieve tests in the millions-of-users levels at commodity prices.

Repurposing Methodology and Architecture for AIQ Integrations

Last reviewed: October 2, 2026

Use this article to plan when existing automation assets can be repurposed for AIQ integrations instead of rebuilt from scratch.

What changed in this article

• Reframed the page as integration planning guidance rather than an abstract methodology note.
• Added checks for asset ownership, current relevance, dependency health, data compatibility, runtime support, and maintenance cost.
• Added decision guidance for reuse, refactor, migration, or retirement of existing assets.

Validation workflow

1. Inventory the existing asset, its owner, runtime, dependencies, data inputs, and known limitations.
2. Decide whether the asset should be reused as-is, refactored, migrated, or retired.
3. Validate the repurposed asset in AIQ with clear evidence and a maintenance owner.

Review note: This page now supports practical integration decisions instead of generic architecture language.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

Test Workshop Tutorial

Recommended guidance

Use workshop tutorials to teach a focused AIQ workflow with clear prerequisites, expected outcomes, and cleanup steps. Keep tutorials current with Scenario Editor, Service Suite, AISG, and Test Node terminology.

Tutorial structure

• Objective, audience, prerequisites, and estimated time.
• Environment, accounts, data, browser, and access requirements.
• Step-by-step workflow with expected results at each checkpoint.
• Troubleshooting notes and cleanup/reset instructions.

Quality checks

1. Run the tutorial end-to-end before publishing updates.
2. Remove obsolete screenshots, old navigation labels, and unsupported feature names.
3. Use sample data that does not expose customer information.
4. Document follow-up learning paths or related articles.

Last updated: October 7, 2026

Data-Driven Test Development in AIQ

Last reviewed: September 30, 2026

Use this article to plan AIQ tests that separate reusable scenario logic from controlled test data.

What changed in this article

• Modernized the broad data-driven testing article around Scenario Editor and AIQ data sources.
• Added guidance for choosing CSV, DPL, service responses, or integration-provided data based on ownership and refresh needs.
• Added validation checks for row coverage, negative cases, cleanup, deterministic replay, and report traceability.

Validation workflow

1. Identify which values belong in the scenario and which should come from controlled data sources.
2. Choose the data source that matches the refresh, security, and ownership requirements.
3. Run at least one positive, negative, and boundary row and confirm each row is visible in results.

Review note: This article now acts as planning guidance instead of a generic data-driven testing overview.

---

Last updated: September 30, 2026

If you have feedback on this topic, contact documentation@appvance.ai.

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

1. Confirm whether the Selenium IDE artifact is still needed or can be rebuilt in Scenario Editor.
2. Validate exported commands and locators before importing or translating them.
3. 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.

Review Selenium Commands and Results in AIQ

Review Selenium Commands and Results in AIQ

Use Selenium command and result details when troubleshooting imported or integrated Selenium executions. This content is legacy-adjacent and should support maintenance of existing Selenium assets, while new functional automation should prefer current Scenario Editor guidance where appropriate.

What to review

• Command names, target locators, and values used during execution.
• Failure messages and the first command that produced a meaningful error.
• Screenshots, logs, or output attached to the execution.
• Differences between local Selenium behavior and AIQ execution behavior.

Maintenance notes

1. Update brittle locators before rerunning under load or in a suite.
2. Replace fixed sleeps with waits that prove the application is ready.
3. Document whether the asset remains maintained or is being migrated to Scenario Editor.

Last updated: September 8, 2026

Maintain TestNG Framework Scripts in AIQ

Maintain TestNG Framework Scripts in AIQ

Use this article for existing TestNG framework scripts that still need to run through AIQ integrations. Treat this as maintenance guidance for legacy or specialized assets, not as the default path for new Scenario Editor tests.

Recommended structure

• Keep test logic, test data, and environment configuration separate.
• Use build tooling to produce repeatable artifacts.
• Store credentials and environment values in approved secure configuration locations.
• Record the framework version and dependency versions with the artifact.

Validation workflow

1. Run the TestNG suite locally or in CI before executing from AIQ.
2. Confirm required dependencies are packaged or available on the execution host.
3. Review AIQ output for classpath, browser, data, or environment failures.
4. Document migration candidates when Scenario Editor can cover the same flow.

Last updated: September 8, 2026

Selenium Integration FAQ for AIQ

Use this FAQ to answer common questions about maintaining Selenium-based assets that interact with AIQ workflows.

What changed in this article

• Changed the title from “Selenium Q&A” to a clearer AIQ-scoped FAQ.
• Aligned the page with the Selenium Integration Reference article and avoided treating Selenium as a standalone topic.
• Added checks for ownership, browser/driver compatibility, framework dependencies, data handoff, reporting, and migration planning.

Validation workflow

1. Confirm the Selenium asset, framework, browser driver, and owner before troubleshooting.
2. Validate the asset outside and inside the AIQ workflow so failures are assigned to the right layer.
3. Document whether the Selenium coverage will be maintained, migrated to Scenario Editor, or retired.

Review note: This FAQ now complements the Selenium integration reference instead of duplicating generic Selenium content.

---

Last updated: October 2, 2026

If you have feedback on this topic, contact documentation@appvance.ai.