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.
Common Commands/API
- CLI: Run a workflow with parallel sharding:
openclaw testing-ci run --workflow my-repo/tests.yml --parallel 4 --token $GITHUB_TOKEN
- CLI: Quarantine flaky tests:
openclaw testing-ci quarantine --pattern "flaky-*" --report junit.xml
- API: Create a workflow: POST /api/skills/testing-ci/workflows with JSON body:
{"name": "build", "matrix": {"shards": [1,2,3,4]}}
- API: Get coverage report: GET /api/skills/testing-ci/coverage?gate=80
- Code snippet (YAML config for GitHub Actions):
jobs:
test:
strategy:
matrix:
shard: [1, 2, 3, 4]
run: npm test --shard=${{ matrix.shard }}/4
- Code snippet (Shell script to handle flaky tests):
if grep -q "flaky" junit.xml; then
openclaw testing-ci quarantine --file junit.xml
fi
Integration Notes
Integrate with GitHub by providing a personal access token in $GITHUB_TOKEN for API calls. For JUnit/Allure reports, ensure your workflow outputs XML files and upload them via GitHub Actions artifacts. Use parallel sharding by defining matrices in workflow YAML, then trigger via OpenClaw: openclaw testing-ci dispatch --repo owner/repo --ref main. For coverage gates, integrate with services like Codecov by adding a step in your workflow: curl -Os codecov.io/bash && bash codecov -t $CODECOV_TOKEN. Always validate inputs to avoid errors, such as checking if $GITHUB_TOKEN is set.
Error Handling
Handle workflow failures by checking exit codes in scripts (e.g., if $? != 0, retry with openclaw testing-ci rerun --workflow ID). For API errors, parse responses for status codes (e.g., 401 for auth issues, resolve by verifying $GITHUB_TOKEN). In parallel runs, use sharding to isolate failures; quarantine flaky tests to prevent false negatives. Common issues: Invalid YAML syntax—validate with yamllint before running; coverage gate failures—adjust thresholds via config flags like --gate 75.
Concrete Usage Examples
- Set up parallel CI for a Node.js repo: Create a workflow file, then run:
openclaw testing-ci run --workflow .github/workflows/tests.yml --parallel 4 --token $GITHUB_TOKEN. This shards tests across 4 runners, reducing execution time from 10m to 3m, and generates a JUnit report for analysis.
- Quarantine and report flaky tests: After a failed run, execute:
openclaw testing-ci quarantine --report allure-results.xml --pattern "test_flaky_*". This isolates flaky tests, reruns them, and integrates the Allure report into your GitHub workflow for visual debugging.
Graph Relationships
- Related to cluster: "testing" (e.g., links to skills like "unit-testing" for deeper test implementation).
- Tagged with: "ci-cd" (connects to "deployment" skills), "github-actions" (integrates with "repo-management"), "parallel" (shares with "scalability" tools), "flaky" (links to "error-analysis"), "testing" (groups with "test-automation").
1---2name: testing-ci3description: CI/CD: GitHub Actions workflows, parallel sharding, flaky quarantine, junit XML/Allure, coverage gates4---5
6# testing-ci
7
8## Purpose
9This 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.
10
11## When to Use
12Use 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.
13
14## Key Capabilities
15- Configure GitHub Actions workflows with parallel sharding using the `matrix` strategy in YAML.
16- Quarantine flaky tests by marking them in reports and rerunning subsets automatically.
17- Generate JUnit XML reports via tools like `junit-report` or Allure for detailed test insights.
18- Enforce coverage gates with thresholds (e.g., >80% line coverage) using tools like Codecov.
19- Integrate with GitHub APIs for workflow dispatching and status checks, requiring authentication via `$GITHUB_TOKEN`.
20
21## Usage Patterns
22Invoke 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.
23
24## Common Commands/API
25- CLI: Run a workflow with parallel sharding: `openclaw testing-ci run --workflow my-repo/tests.yml --parallel 4 --token $GITHUB_TOKEN`
26- CLI: Quarantine flaky tests: `openclaw testing-ci quarantine --pattern "flaky-*" --report junit.xml`
27- API: Create a workflow: POST /api/skills/testing-ci/workflows with JSON body: `{"name": "build", "matrix": {"shards": [1,2,3,4]}}`
28- API: Get coverage report: GET /api/skills/testing-ci/coverage?gate=80
29- Code snippet (YAML config for GitHub Actions):
30 ```
31 jobs:
32 test:
33 strategy:
34 matrix:
35 shard: [1, 2, 3, 4]
36 run: npm test --shard=${{ matrix.shard }}/4
37 ```
38- Code snippet (Shell script to handle flaky tests):
39 ```
40 if grep -q "flaky" junit.xml; then
41 openclaw testing-ci quarantine --file junit.xml
42 fi
43 ```
44
45## Integration Notes
46Integrate with GitHub by providing a personal access token in `$GITHUB_TOKEN` for API calls. For JUnit/Allure reports, ensure your workflow outputs XML files and upload them via GitHub Actions artifacts. Use parallel sharding by defining matrices in workflow YAML, then trigger via OpenClaw: `openclaw testing-ci dispatch --repo owner/repo --ref main`. For coverage gates, integrate with services like Codecov by adding a step in your workflow: `curl -Os codecov.io/bash && bash codecov -t $CODECOV_TOKEN`. Always validate inputs to avoid errors, such as checking if `$GITHUB_TOKEN` is set.
47
48## Error Handling
49Handle workflow failures by checking exit codes in scripts (e.g., if `$? != 0`, retry with `openclaw testing-ci rerun --workflow ID`). For API errors, parse responses for status codes (e.g., 401 for auth issues, resolve by verifying `$GITHUB_TOKEN`). In parallel runs, use sharding to isolate failures; quarantine flaky tests to prevent false negatives. Common issues: Invalid YAML syntax—validate with `yamllint` before running; coverage gate failures—adjust thresholds via config flags like `--gate 75`.
50
51## Concrete Usage Examples
521. **Set up parallel CI for a Node.js repo**: Create a workflow file, then run: `openclaw testing-ci run --workflow .github/workflows/tests.yml --parallel 4 --token $GITHUB_TOKEN`. This shards tests across 4 runners, reducing execution time from 10m to 3m, and generates a JUnit report for analysis.
532. **Quarantine and report flaky tests**: After a failed run, execute: `openclaw testing-ci quarantine --report allure-results.xml --pattern "test_flaky_*"`. This isolates flaky tests, reruns them, and integrates the Allure report into your GitHub workflow for visual debugging.
54
55## Graph Relationships
56- Related to cluster: "testing" (e.g., links to skills like "unit-testing" for deeper test implementation).
57- Tagged with: "ci-cd" (connects to "deployment" skills), "github-actions" (integrates with "repo-management"), "parallel" (shares with "scalability" tools), "flaky" (links to "error-analysis"), "testing" (groups with "test-automation").
majiayu000