release-openclaw-plugin-testing

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# OpenClaw Pre-Release Plugin Testing

Use this skill when the user asks for plugin release confidence, plugin lifecycle
sweeps, package-artifact plugin proof, or "what else should we test before
release?" It complements `openclaw-testing`; use that skill too when choosing
the cheapest safe runner or debugging a failing lane.

## Goal

Prove the plugin system as a product surface, not just as source tests:

- bundled plugin lifecycle: install, inspect, enable, disable, uninstall
- package artifact behavior from a clean `HOME`
- doctor/fix/config validation and idempotence
- config discovery and config round-trip
- status/log visibility and diagnostics
- gateway startup/bootstrap with plugin metadata snapshots
- public SDK compatibility for real external plugins
- live-ish provider/channel probes only when safe credentials exist

## First Checks

From the OpenClaw repo root:

```bash
pnpm docs:list
git status --short --branch
pnpm changed:lanes --json
```

Follow [`openclaw-testing`](../openclaw-testing/SKILL.md) for dependency
ownership and the choice of local or remote proof.

## Runner Choice

Prefer this order:

1. **GitHub Package Acceptance** for installable-package product proof.
2. **Current dedicated Linux worker** for trusted source/package/Docker proof
   when it has the required dependencies and capabilities.
3. **`ci-build-artifacts-testbox.yml` Testbox** when Docker/package lanes need
   seeded `dist`, `dist-runtime`, and package caches.
4. **`ci-check-testbox.yml` Testbox** for source checks, targeted Vitest,
   package-boundary checks, or focused Docker lanes.
5. **Workstation targeted commands only** for small format/static/unit probes.

Avoid long package Docker runs from a stale sparse worktree. If Testbox sync
reports hundreds of changed files or starts deleting package inputs, stop and
warm a fresh box from current `main`, or switch to Package Acceptance.

## Existing Baseline

Run or verify these before inventing new coverage:

```bash
OPENCLAW_TESTBOX=1 pnpm check:changed
pnpm run test:extensions:package-boundary:canary
pnpm run test:extensions:package-boundary:compile
pnpm test:docker:plugins
OPENCLAW_PLUGINS_E2E_CLAWHUB=0 pnpm test:docker:plugins
pnpm test:docker:plugin-update
```

For full bundled install/uninstall proof, shard the packaged sweep:

```bash
OPENCLAW_BUNDLED_PLUGIN_SWEEP_TOTAL=8 \
OPENCLAW_BUNDLED_PLUGIN_SWEEP_INDEX=<0-7> \
pnpm test:docker:bundled-plugin-install-uninstall
```

This example partitions the selected package's plugin inventory over shards `0-7`.
Private QA plugins are source-mode only unless a package explicitly includes
them.

## Confidence Matrix

Use this matrix for pre-release signoff. Record pass/fail, run URL/Testbox ID,
package SHA/version, and skipped-live reason.

| Surface           | Proof                                                           | Preferred runner                     |
| ----------------- | --------------------------------------------------------------- | ------------------------------------ |
| Package artifact  | Package Acceptance `suite_profile=package` or custom lanes      | GitHub Actions                       |
| Bundled lifecycle | Sharded `test:docker:bundled-plugin-install-uninstall`          | Testbox or release Docker            |
| External plugins  | `test:docker:plugins` and `plugins-offline`                     | Testbox/package acceptance           |
| Update no-op      | `test:docker:plugin-update`                                     | Testbox/package acceptance           |
| Doctor/fix        | seeded bad configs + `doctor --fix --non-interactive`           | new Docker/Testbox harness           |
| Config round-trip | `config set/get`, inspect, doctor, reload, diff hash            | new Docker/Testbox harness           |
| Gateway bootstrap | clean `HOME`, plugin groups enabled/disabled, status JSON       | new Docker/Testbox harness           |
| SDK compatibility | directory, tgz, and `file:` external plugins using SDK subpaths | `test:docker:plugins` plus new smoke |
| Live-ish          | redacted provider/channel probes only for present env           | Testbox live lanes                   |

## Package Acceptance Plan

Full Release Validation owns final candidate qualification with Q=C and the
exact publication tarballs. Use standalone Package Acceptance for diagnostics
or postpublish confidence, not as a replacement candidate qualification:

```bash
gh workflow run package-acceptance.yml \
  --repo openclaw/openclaw \
  --ref main \
  -f workflow_ref=main \
  -f source=ref \
  -f package_ref=<branch-or-sha> \
  -f suite_profile=custom \
  -f docker_lanes='plugins-offline plugin-update doctor-switch update-channel-switch config-reload mcp-channels npm-onboard-channel-agent' \
  -f telegram_mode=mock-openai
```

Use `source=npm -f package_spec=openclaw@beta` for published beta proof. These
standalone diagnostic/confidence runs may use trusted current harness code;
candidate qualification must retain the frozen candidate's harness instead.

For extended-stable shared publication, require complete exact-target Full
Release Validation from the admitted candidate-owned `release-ci/*` harness at Q=C,
with trusted P admission and publication tooling separate. Direct
canonical-branch or `main` producers do not satisfy the protected publisher.
Package Acceptance is a post-publish selector smoke:

From openclaw/openclaw, MIT.

More from openclaw/openclaw