bmad-testarch-ci

Automated CI/CD pipeline setup with parallel test execution uses sharding to distribute tests and burn-in loops to detect flaky tests. It generates pipeline configurations that handle test framework setup, artifact collection, and quality gates across multiple CI platforms.

Yes, CI/CD pipeline setup supports GitHub Actions, GitLab CI, Azure DevOps, Harness, and Circle CI. It generates platform-specific configurations for test execution, quality gates, and artifact collection tailored to your chosen CI platform.

Burn-in loops execute tests repeatedly within CI pipelines to identify intermittent flaky test failures. This automated detection mechanism runs alongside parallel test execution and quality gates to ensure code quality before deployment.

Quality gates for contract testing verify provider compliance during CI/CD pipeline setup. The configuration automates deployment verification and contract testing alongside parallel test execution, ensuring all quality criteria pass before code promotion.

Automating test execution and quality gates across multiple CI platforms requires unified pipeline configuration generation. This approach handles parallel test sharding, burn-in loops, and contract testing for GitHub Actions, GitLab CI, Azure DevOps, Harness, and Circle CI simultaneously.

CI/CD pipeline automation requires test framework setup, CI platform configuration, and artifact collection mechanisms. You need an existing test framework in your project before the pipeline can automate parallel execution, burn-in loops, and quality gate enforcement.