testing

Purpose

This skill enables OpenClaw to assist with comprehensive testing strategies, including the testing pyramid (unit, integration, e2e), TDD/BDD methodologies, code coverage analysis, and naming conventions to ensure high-quality code. It focuses on integrating testing into development workflows for robust software.

When to Use

Use this skill when writing or reviewing code that requires test-driven development, such as implementing new features in a project, debugging failures, or ensuring coverage thresholds. Apply it in scenarios like agile sprints, CI/CD pipelines, or when refactoring code to maintain quality.

Key Capabilities

• Generate unit tests using TDD: Create tests for functions with assertions based on input/output.
• Support BDD with Gherkin syntax: Parse feature files and generate step definitions.
• Analyze testing pyramid: Recommend distribution (e.g., 70% unit, 20% integration, 10% e2e).
• Enforce coverage strategies: Set thresholds (e.g., >80%) and identify uncovered lines.
• Apply naming conventions: Enforce patterns like testFunctionName for tests.
• Integrate with tools: Use APIs to run tests via Jest, Pytest, or Selenium.

Usage Patterns

To use this skill, invoke OpenClaw with specific commands in your chat or script. Start by providing code snippets for analysis, then request test generation. For TDD, alternate between writing tests and code. In BDD, supply user stories first. Always specify the test type (unit, integration, e2e) to tailor outputs. Configure via a JSON file, e.g., set "coverageThreshold": 80 in .openclaw/config.json. For automation, chain with build tools like Make or npm scripts.