Test Patterns

Write and run tests across languages and frameworks. Use when setting up test suites, writing unit/integration/E2E tests, measuring coverage, mocking dependencies, or debugging test failures. Covers Node.js (Jest/Vitest), Python (pytest), Go, Rust, and Bash.

This skill is an offline guide with examples for writing and running tests — it is internally consistent. Before using: ensure the appropriate runtimes (node, python3, go, cargo, bash) are installed as needed; be aware that running tests in a repository will execute the repository's code (including network calls, DB interactions, or any side effects), so run tests in an isolated/sandboxed environment or with mocks when executing untrusted code. Also review any package installs (npm/pip) that test suites require, since installing dependencies can pull third-party code. The skill itself does not request secrets or perform installs, but the tests you run based on its instructions may interact with external services — audit those test cases accordingly.

Type: OpenClaw Skill Name: test-patterns Version: 1.0.0 The skill is classified as suspicious due to the inherent high-risk nature of its core functionality and the inclusion of powerful shell primitives. The `SKILL.md` provides extensive examples of executing shell commands and code in various languages (Node.js, Python, Go, Rust, Bash), which is explicitly declared in the `requires` metadata (`anyBins: ['node', 'python3', 'go', 'cargo', 'bash']`). While this aligns with the stated purpose of 'running tests across languages', it grants broad system access. Specifically, the Bash test runner example includes `eval "$cmd"`, a dangerous primitive that, while presented as a template with benign examples, could lead to arbitrary command execution if the agent were to use it with untrusted input or if the skill were modified to inject malicious commands into `$cmd`.