# Running Tests from Your CI/CD Pipeline

KushoAI provides comprehensive CI/CD integration for automated API testing using Docker containers. This enables seamless testing of your APIs and E2E workflows at every stage of your development pipeline with consistent, reliable execution across all platforms.

All CI/CD test execution in KushoAI is powered by Docker containers, ensuring consistent behavior across different platforms and environments. The Docker-based test runner supports multiple execution modes and integrates seamlessly with popular CI/CD platforms.

1. API Test Suite Execution by UUID - Execute specific test suites using their unique identifiers
2. API Test Suite Execution by Group ID - Run all test suites within a specific group
3. API Test Suite Execution by Tags - Filter and execute test suites based on tags
4. E2E Workflow Execution - Execute end-to-end workflows with execution profiles

KushoAI supports all major CI/CD platforms through Docker integration:

• GitHub Actions - Native GitHub workflow integration
• GitLab CI/CD - GitLab pipeline integration with Docker-in-Docker support
• Jenkins - Jenkins pipeline integration with Docker support
• Azure DevOps - Azure pipeline integration with Docker tasks
• AWS CodeBuild - Amazon CodeBuild integration with Docker environments
• CircleCI - Circle CI integration with Docker executors
• Travis CI - Travis CI integration with Docker support

The Kusho test runner is distributed as a Docker image available at:

public.ecr.aws/y5g4u6y7/kusho-test-runner:latest

All test execution follows the same Docker run pattern:

docker run --rm \
  -e BASE_URL="https://be.kusho.ai" \
  -e ENVIRONMENT_ID="your-env-id" \
  -e API_KEY="your-api-key" \
  -e CI_COMMIT_SHA="commit-hash" \
  -e CI_COMMIT_MESSAGE="commit message" \
  -e [EXECUTION_MODE_VARIABLES] \
  public.ecr.aws/y5g4u6y7/kusho-test-runner:latest

To integrate Kusho testing into your CI/CD pipeline:

1. Get your API credentials from the KushoAI dashboard under Manage Workspace > API Keys tab
2. Identify your test suites - UUIDs, group IDs, or tags. These can be copied from their respective locations on UI.
3. Configure secrets - Add your API key and other sensitive data as secrets to your CI/CD platform.
4. Add the workflow - Use our platform-specific examples as starting points

On the Home page, click on the "CI/CD" button to access platform-specific setup instructions and examples or refer the platform specific instructions section in docs.

After clicking the CI/CD button, select your desired platform to get detailed setup instructions tailored for your specific CI/CD environment.

For detailed setup instructions for your specific platform, you can also refer:

• Platform-Specific Instructions
• General Instructions and Configuration