Skip to main content

Test Orchestrator CI/CD Integration

Overview​

The Test Orchestrator is designed to be embedded directly into your CI/CD pipelines, acting as a quality gate during the Test stage. By automating orchestration and retries at the runtime level, the agent ensures that environmental flakiness does not block your delivery pipeline. It provides a seamless way to integrate with your existing test automation framework while giving you the flexibility to manage execution parameters centrally.

Pipeline Flow​

The following lifecycle describes how the Test Orchestrator interacts with standard CI/CD runners (Example, Jenkins, GitHub Actions, or GitLab):

  1. Code commit triggers CI
  2. Build is created
  3. Test Orchestrator executes tests
  4. Results determine pipeline outcome

Pipeline Flow

Integration Steps​

To integrate the Test Orchestrator into your automated workflow, follow these steps:

  1. Add Test Orchestrator JAR to your project
  2. Configure YAML file
  3. Update Gradle test task:
    • Add JAR path
    • Add config file path
  4. Run pipeline

Related documentation:

Last updated on