skills.rest
borealBytes
borealBytesCOMMUNITY
Explore all skills by this author →
GitHub

openclaw-testing

Select minimal OpenClaw tests for local, CI, Docker E2E, and release validation.

7|12|Updated Mar 10, 2026
Search Tags:#vitest#testing#debugging#docker#ci#rerun#openclaw
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-testing-borealbytes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-testing
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/openclaw-testing
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-testing-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Decide what to test, debug failures, and validate changes without wasting hours.

Core Features & Use Cases

  • Local Test Shortcuts: quickly run and re-run only the touched tests using dedicated scripts and pnpm wrappers.
  • Command Semantics: clear, deterministic rules for what to test and how to prove changes.
  • Routing Model: guided workflows to focus proofs on the affected surfaces (CI, Docker E2E, and release checks).

Quick Start

Run a focused test pass for the touched surface using the local shortcuts and the crabbox wrapper to verify changes quickly.

Frequently Asked Questions about openclaw-testing

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

FAQPage Schema
How do I run targeted OpenClaw tests for touched code instead of the entire suite?▼

Run targeted OpenClaw tests for touched code using local test shortcuts and pnpm wrappers to validate changes quickly. This enforces fast local runs by selecting only the affected tests, avoiding the full suite.

Can I use this to rerun failed vitest cases in a CI pipeline?▼

Yes, you can rerun failed vitest cases in a CI pipeline. The routing model provides deterministic command semantics to focus proofs on affected surfaces, ensuring CI reruns validate only the necessary changes.

What is the best way to validate OpenClaw patches across multiple worktrees?▼

The best way to validate OpenClaw patches across worktrees is applying deterministic routing rules to select minimal tests. This focuses proofs on affected surfaces, ensuring release validation without redundant executions.

Does this testing approach work with Docker E2E lanes?▼

Yes, this testing approach works with Docker E2E lanes. The routing model guides workflows to focus proofs on affected Docker surfaces, ensuring deterministic release checks without running unnecessary end-to-end tests.

Why should I avoid running the entire OpenClaw test suite during debugging?▼

Avoiding the entire OpenClaw test suite during debugging prevents wasted hours. Guardrails enforce targeted proofs and fast local runs, ensuring you validate only the touched surfaces for quick feedback.

Do I need specific scripts to identify the minimal OpenClaw tests for my changes?▼

Yes, dedicated scripts identify the minimal OpenClaw tests needed for your changes. These scripts provide local test shortcuts and command semantics to route proofs effectively across CI and Docker lanes.

Related Skills

Explore More Software Engineering Skills→
p-sree-sai-pavanp-sree-sai-pavan
5

crabbox

Automate remote OpenClaw validation workflows with Crabbox across providers and leases.

Community
Advanced
vignesh2027vignesh2027
18

openclaw-testing

Manage OpenClaw test selection, debugging, CI checks, and Docker E2E lane verification.

Community
Advanced
AztecProtocolAztecProtocol
449

fix-pr

Analyze CI logs and apply targeted fixes to failing PRs.

Official
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced