testing-ci

Purpose

This skill automates CI/CD pipelines using GitHub Actions, focusing on testing workflows. It handles parallel test execution, quarantines flaky tests, generates reports in JUnit XML or Allure formats, and enforces coverage gates to ensure code quality in repositories.

When to Use

Use this skill when setting up or optimizing CI for GitHub repos, especially for projects with large test suites (e.g., >1000 tests), to reduce run times via parallel sharding. Apply it for flaky test management in unstable environments or when integrating coverage checks before merges.

Key Capabilities

• Configure GitHub Actions workflows with parallel sharding using the matrix strategy in YAML.
• Quarantine flaky tests by marking them in reports and rerunning subsets automatically.
• Generate JUnit XML reports via tools like junit-report or Allure for detailed test insights.
• Enforce coverage gates with thresholds (e.g., >80% line coverage) using tools like Codecov.
• Integrate with GitHub APIs for workflow dispatching and status checks, requiring authentication via $GITHUB_TOKEN.

Usage Patterns

Invoke this skill via OpenClaw CLI commands prefixed with openclaw testing-ci. For API usage, send requests to the OpenClaw endpoint (e.g., POST /api/skills/testing-ci). In code, embed it in scripts by checking for the skill ID and passing parameters like workflow names or test shards. Always set environment variables for secrets, such as $GITHUB_TOKEN, before execution. For parallel testing, define shards in your workflow YAML and trigger runs programmatically.