AIQ CI/CD Overview

Recommended guidance

Use AIQ CI/CD integrations to run controlled Scenario Editor, Service Suite, and performance checks from automated delivery pipelines. CI/CD jobs should provide repeatable execution, clear pass/fail criteria, and useful evidence without exposing credentials or customer data.

What to define before automation

• The AIQ environment, project, scenario or suite, target Test Node, and browser or API execution mode.
• The pipeline trigger: pull request, merge, scheduled run, release candidate, or production validation.
• The test data source, expected result, timeout, retry policy, and artifact retention.
• The credential model, using CI/CD secret storage instead of hard-coded values.
• The owner responsible for failures, flaky tests, and pipeline maintenance.

Recommended pipeline behavior

1. Run a small smoke suite before expensive end-to-end or performance suites.
2. Fail the pipeline when AIQ cannot start, times out, or returns a failed result.
3. Publish links to AIQ executions, logs, reports, screenshots, and service responses.
4. Separate product failures from environment, data, browser, and integration failures.
5. Review duplicate or obsolete CI/CD jobs regularly and retire unused jobs.

Last updated: October 5, 2026