test-runner

What This Skill Does

The test-runner skill serves as a sophisticated automated testing orchestrator for the OpenClaw AI agent. It is designed to handle the entire lifecycle of software verification, spanning language detection, dependency management, test execution, and debugging via a structured red-green-refactor cycle. By abstracting the complexities of configuring frameworks like Vitest, Jest, pytest, XCTest, and Playwright, the agent allows developers to maintain high code quality with minimal manual intervention. It excels at determining the appropriate test scope—running narrow unit tests first to isolate bugs before verifying system-wide functionality.

Installation

To integrate this skill into your environment, run the following command within your project context: clawhub install openclaw/skills/skills/alexwoo-awso/test-runner-codex

Use Cases

1. Automated Regression Testing: Ensuring new code changes do not break existing functionality in legacy repositories.
2. TDD Workflow Implementation: Systematically guiding the development process from failing test cases to robust, production-ready code.
3. Framework Standardization: Automatically scaffolding standard testing configurations (like Vitest for TypeScript) in greenfield projects.
4. Debugging Complex API Flows: Automating the verification of complex integration flows using Playwright or pytest+httpx.

Example Prompts

1. "Look at my existing project, set up the appropriate testing framework if it's missing, and run all unit tests."
2. "I am encountering a bug in the user authentication module. Please write a failing unit test that reproduces this issue, then fix the code to pass it."
3. "Run only the payment processing tests and generate a coverage report for the repository."

Tips & Limitations

• Safety First: The agent operates based on the local project configuration. Always review the generated code changes via Git before committing.
• Framework Priority: The skill is programmed to prioritize the project's existing test stack. Do not force a new framework unless the project lacks one entirely to avoid configuration bloat.
• Scope Management: Always start with the smallest possible test scope to save time and reduce noise in CI pipelines. If you are dealing with complex mocks, rely on the built-in patterns for Vitest or pytest as documented to maintain cleaner, more readable test suites.