qa-ci-integration
CI/CD test pipelines for GitHub Actions, GitLab CI/CD and Jenkins: matrix builds, sharding, retries, test reports, and artifact handling. Shared conventions cover when to shard and retry, flake quarantine, and per-trigger cadence, with CircleCI patterns in references. A critic agent (ci-pipeline-health-critic) flags test-pipeline anti-patterns such as retries that mask flakiness.
/plugin install qa-ci-integration@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Tooling
- Version
v1.2.4- Contents
- 4 skills · 1 agent
Skills4
ci-test-job-conventionsUse when designing how tests run in CI on any platform (GitHub Actions, GitLab CI, Jenkins, CircleCI): how many shards, which failures are safe to retry, quarantine, artifact retention, per-PR vs nightly cadence, cancel-on-push, timeouts and secrets.skillgithub-actions-test-jobsUse whenever the task is to run tests in GitHub Actions: a test workflow on pull requests, matrix builds across OS and runtime versions, splitting a suite across parallel runners, service containers such as Postgres or Redis, uploading JUnit reports, and trigger filters.skillgitlab-ci-test-jobsUse whenever the task is to run tests in GitLab CI/CD: test stages in .gitlab-ci.yml, parallel matrix jobs, junit and coverage artifact reports, Postgres or Redis services, needs between jobs, rules for triggers and retry policy.skilljenkinsfile-test-stagesUse whenever the task is to run tests in Jenkins: declarative Jenkinsfile test stages, parallel stages across agents, post always/failure actions, JUnit report publishing and lockable resources for shared test infrastructure.skill
Agents1
About qa-ci-integration
CI/CD test workflow patterns per platform: GitHub Actions, GitLab CI/CD, Jenkins. Each platform's matrix builds, artifact handling, retry policies, sharding, JUnit reporting. Plus cross-CI conventions reference (when to shard, retry policy, flake quarantine integration, artifact lifecycle) that also carries the CircleCI test-config patterns in its references/.
Related reading
- Playwright 1.65 Changes How Page Object Fields Initialize
- Which Test Data Isolation Strategy Fits a Shared Database?
- Playwright Test Agents: Run the Healer Without Losing CI Signal
- Playwright Visual Tests That Pass in CI for the Right Reasons
- Playwright in GitHub Actions: Docker, Failure Capture, and Worker Parallelism
- Flaky Playwright Tests: Five Root Causes and Fixes
- How to Run Automated Tests in GitHub Actions
- Playwright vs Cypress vs Selenium: 2026 Edition
- Setting Up Playwright with TypeScript from Scratch