一键导入
helm-test
Use when the user wants to run, choose, or interpret Helm test and check commands across the PHP, JavaScript, TypeScript, or Playwright toolchains.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when the user wants to run, choose, or interpret Helm test and check commands across the PHP, JavaScript, TypeScript, or Playwright toolchains.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to run or interpret Helm benchmark commands, compare benchmark reports, or summarize REST API performance regressions and improvements.
Use when the user wants to prepare a Helm git commit, choose a commit type, or format a commit message using the repo's commit conventions.
Use when the user wants to define, refine, or draft a Helm task file in .plans/tasks using the repo's naming, metadata, and writing conventions.
| name | helm-test |
| description | Use when the user wants to run, choose, or interpret Helm test and check commands across the PHP, JavaScript, TypeScript, or Playwright toolchains. |
Helm has parallel PHP and JS toolchains. PHP runs under WordPress via slic (Docker). JS runs directly via Vitest and Playwright.
PHP tests use Codeception through wp-browser, executed with slic. slic run is a thin wrapper around codecept run, so any codecept run syntax works.
codecept run [options] [--] [<suite> [<test>]]
The <test> argument is a path relative to the suite directory (tests/Wpunit/), optionally followed by :methodName.
slic run Wpunit # all Wpunit tests
slic run Wpunit ShipLink # a directory
slic run Wpunit ShipLink/HexCoordinateTest.php # a single file
slic run Wpunit ShipLink/HexCoordinateTest.php:testDistanceCalculation # a single method
slic run Wpunit --filter=testDistance # filter by name pattern
slic run Wpunit --group=slow # run a Codeception group
slic run Wpunit --debug # verbose scenario output
slic cc build # rebuild Codeception actors after changing test helpers
One-time slic setup from ~/Projects: slic here && slic use helm. After that, slic run works from the project directory.
composer analyse # PHPStan
composer lint # PHPCS
composer lint:fix # PHPCBF (auto-fix)
These run PHP binaries directly with no Docker dependency, so they work anywhere Composer is installed.
bun run test # Vitest unit tests
bun run test:watch # Vitest watch mode
bun run check-types # tsc --noEmit
bun run lint:js # ESLint
bun run lint:fix # ESLint auto-fix
Playwright runs against a Vite dev server. It does not need a running WordPress instance.
bun run test:e2e # headless
bun run test:e2e:ui # interactive UI
bun run test:e2e:headed # headed browser
bun run test:e2e:debug # Playwright inspector
bun run test:e2e:report # open last report
Run PHP static checks, PHP unit tests, then JS checks and unit tests:
composer analyse && composer lint && slic run Wpunit && bun run check-types && bun run lint:js && bun run test
Run Playwright separately when UI behavior changed.