Automate CI/CD pipeline setup with test execution and quality gates.
npx skills add https://github.com/tiween/tiween --skill bmad-testarch-ci-tiween
Please help me install this Agent Skill. Skill: bmad-testarch-ci Source: https://github.com/tiween/tiween/tree/main/.agents/skills/bmad-testarch-ci Command: npx skills add https://github.com/tiween/tiween --skill bmad-testarch-ci-tiween
This Skill automates the setup of CI/CD pipelines with test execution, quality gates, and burn-in loops, eliminating the need for manual configuration and reducing the risk of human error.
Run the 'bmad-testarch-ci' skill to automatically set up a CI/CD pipeline for your project.
High-intent search queries and answers about installing and using this skill.
Automating CI/CD pipeline setup for test execution involves configuring continuous integration platforms to automatically trigger test suites. This eliminates manual configuration, reduces human error, and validates code quality during software development workflows.
Detecting flaky tests in continuous integration is best achieved by configuring burn-in loops. Burn-in loops repeatedly execute test suites to identify inconsistent failures, allowing teams to set reliable quality gates for code releases.
Yes, you can execute automated tests in parallel on GitHub Actions or GitLab CI by implementing test sharding. Sharding divides test runs across multiple runners, maximizing efficient resource utilization and reducing overall pipeline execution time.
Yes, this CI/CD automation approach supports Jest and Vitest for configuring quality gates. It integrates with these testing tools to establish quality thresholds and automate test execution within your existing software development pipelines.
Configuring quality thresholds in Azure DevOps or Jenkins prevents unstable code from deploying by enforcing automated quality gates. This ensures high-quality code releases by validating that all test executions and burn-in loops pass predefined criteria.
Using Cypress or Playwright for burn-in loops can consume significant CI/CD resources due to repeated browser-based test executions. While effective for flaky test detection, parallel execution with sharding is required to manage resource utilization efficiently.
atanakaGenerate unit, integration, and end-to-end tests from use case specifications and domain models.
ResearchMonkeyAnalyze test quality and coverage to identify gaps and flaky tests.
pluginagentmarketplaceAutomate cloud infrastructure provisioning and deployment with Terraform and Kubernetes.
feliperybaCreate and execute Playwright end-to-end browser tests for QA validation.
