testing-procedures

Automate Catch2 v3 test execution and result reporting for the Kalahari project.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/bartoszwarzocha/kalahari --skill testing-procedures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-procedures
Source: https://github.com/bartoszwarzocha/kalahari/tree/main/.claude/skills/testing-procedures
Command: npx skills add https://github.com/bartoszwarzocha/kalahari --skill testing-procedures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes how to build and run tests across platforms using Catch2, with clear result interpretation.

Core Features & Use Cases

  • Build Commands: Windows and Linux build scripts
  • Test Execution: Platform-specific test commands
  • Test Framework: Catch2 v3 with BDD style
  • Result Interpretation: Clear PASS/FAIL summaries
  • What to Check: Coverage, regressions, and test data considerations
  • Manual Testing: UI and UX verification steps
  • Reporting Results: JSON or structured summaries

Quick Start

Run the Windows build, then execute the tests and review the results in the console output.

Frequently Asked Questions about testing-procedures

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

FAQPage Schema
How do I standardize testing across Windows and Linux with Catch2?

Standardize testing by using platform-specific build scripts and Catch2 v3 with BDD style to ensure consistent test execution and reproducible results across Windows and Linux environments.

How do I automate tests in CI/CD pipelines with Catch2?

Automate tests in CI/CD by integrating prescribed build commands and test execution scripts that produce consistent output formats, enabling reproducible builds and comprehensive coverage checks across platforms.

Can I use Catch2 v3 for BDD-style testing with clear pass/fail results?

Yes. Catch2 v3 supports BDD-style test frameworks with clear PASS/FAIL summaries and structured result interpretation, making it suitable for both automated and manual testing verification.

What should I check after running tests to ensure coverage and catch regressions?

After test execution, check coverage metrics, verify regressions, review test data considerations, and analyze structured JSON or console output summaries to identify actionable diagnostics.

How do I report test results in a structured format for local and CI/CD environments?

Report results using JSON or structured summaries generated from test execution output, enabling consistent diagnostics and actionable feedback across local development and CI/CD pipelines.

Does this approach include manual testing steps alongside automated test execution?

Yes. The standardized procedure covers both automated Catch2 test execution and manual UI/UX verification steps, with comprehensive reporting for both verification methods.