run-tests

Run ctest validation suites on built content under build/.

2.8k|817|Updated Apr 29, 2014
One-click install
npx skills add https://github.com/ComplianceAsCode/content --skill run-tests-complianceascode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/ComplianceAsCode/content/tree/main/.claude/skills/run-tests
Command: npx skills add https://github.com/ComplianceAsCode/content --skill run-tests-complianceascode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates validation testing of built content using ctest and related tooling to ensure builds are correct before deployment.

Core Features & Use Cases

  • Verifies that a build exists under build/ and artifacts are present.
  • Executes the full ctest validation suite across YAML, OVAL, references, and related content checks.
  • Provides clear pass/fail results with remediation guidance for failed tests.
  • Supports deterministic runs via mcp__content-mcp__* tools when available, with a filesystem fallback.

Quick Start

Build a product first using /build-product, then invoke /run-tests to validate the built content.

Frequently Asked Questions about run-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ctest validation for build artifacts in a CI pipeline?

Automate ctest validation for build artifacts by executing the full test suite against built content under build/ to verify correctness before deployment. The Skill runs YAML, OVAL, and references checks, returning pass/fail results with remediation guidance for any failed tests.

Do I need to build a product before running ctest validation?

Yes, you must build a product first so that build artifacts exist under the build/ directory. The ctest validation requires a built product to be present, checking for artifacts like ssg-*-ds.xml files before executing the test suite.

What does ctest validation check when verifying built content?

ctest validation checks built content by running the full test suite across YAML, OVAL, references, and related content checks. It verifies that build artifacts are present and analyzes test results to ensure builds are correct before deployment.

Can I run ctest validation locally for QA without CI pipeline integration?

Yes, you can run ctest validation locally for QA purposes. The Skill supports local QA workflows to verify build artifacts under build/ by running the full test suite and analyzing results, not just CI pipeline automation scenarios.

What happens if mcp content tools are unavailable during ctest validation?

When mcp__content-mcp__* tools are unavailable, the ctest validation falls back to filesystem checks using ls build/ssg-*-ds.xml to verify build artifacts. This ensures validation can proceed deterministically even without the specialized tools.

Why does ctest validation fail when no build directory exists?

ctest validation fails without a build directory because it requires a built product with artifacts present under build/. The Skill verifies the build exists first, checking for files like ssg-*-ds.xml, and cannot run the test suite without built content to validate.