菜单
Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/platonai/Browser4 --skill test-production命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Automatically fills web forms using provided field data and can optionally submit the form. Use when automating form input, testing forms, or submitting structured data to websites.
Extracts data from web pages using browser automation and CSS/JavaScript selectors. Use when you need to scrape titles/text/structured fields from live web pages or when the user mentions scraping, extraction, or selectors.
基于 SOC 职业分类
| name | test-production |
| title | Test Production — Acceptance-test the latest published browser4-cli release |
| description | Runs bin/test-production.ps1 to acceptance-test a production (or prerelease) release of browser4-cli. Use when asked to run production tests, acceptance-test a release, or verify the published CLI. |
| allowed-tools | Bash(pwsh:*), Bash(./bin/test-production.ps1:*) |
Runs bin/test-production.ps1 — an acceptance test that simulates a real end
user's journey with the published browser4-cli release. It downloads,
installs, exercises, uninstalls, and re-installs the global CLI from the public
OSS distribution channel.
This is a separate entrypoint from bin/test.ps1 (covered by the run-tests
skill). test-production.ps1 tests the released artifact — not the
in-repo source — and is designed to be run in CI or locally before tagging a
release.
Running with no arguments shows help (safe default):
./bin/test-production.ps1
| Flag | Description |
|---|---|
-WorkingDir <path> | Working directory for temporary artifacts (default: random subdir under system temp) |
-Stress | Enable the multi-scenario stress suite (opt-in) |
-MultiScenariosIterations <n> | Iterations for the multi-scenario suite (default: 1, only with -Stress) |
-RemoveWorkingDir | Delete the working directory on exit (default: preserved for review) |
-Version <tag> | Test a specific release version (e.g. v4.12.0-rc.1, v4.11.0). Default: latest stable |
-Help | Show help message |
--help, --version, config --help, agent-run --help, invalid command.open), verifies health endpoint responds.close-all, kill-all), verifies it's unreachable.~/.browser4 into the test sandbox.-Stress) Multi-scenarios stress test — runs
browser4-tests/tests-production/multi-scenarios.ps1 against the global CLI.The script acts like a real end user — it does not patch install scripts, create missing symlinks, or manually clean up after uninstall. If any of those are needed, the test fails because a real user would hit the same broken behavior.
The test uses environment variables (BROWSER4_CLI_STATE_DIR, BROWSER4_RUNTIME_DIR)
to route all state and runtime data into an isolated working directory. The
user's real ~/.browser4 is never modified — it is only read to copy config
into the test sandbox during Cycle 2.
# Show help (no arguments = safe default)
./bin/test-production.ps1
# Run the full acceptance test (no stress)
./bin/test-production.ps1
# Run with stress suite
./bin/test-production.ps1 -Stress
# Production CI: stress test with multiple iterations, clean up afterward
./bin/test-production.ps1 -Stress -MultiScenariosIterations 3 -RemoveWorkingDir
# Test a specific prerelease candidate
./bin/test-production.ps1 -Version v4.12.0-rc.1 -Stress
# Test a specific stable release
./bin/test-production.ps1 -Version v4.11.0
# Use a specific working directory (kept for review by default)
./bin/test-production.ps1 -WorkingDir /tmp/my-acceptance-test
# Full acceptance gate for a release
./bin/test-production.ps1 -Stress -MultiScenariosIterations 3 -RemoveWorkingDir
| Code | Meaning |
|---|---|
| 0 | All steps passed |
| 1 | One or more steps failed |
By default, a random subdirectory is created under the system temp directory
(e.g. /tmp/.browser4-acceptance/20260720-143052-a3f2). The directory is
preserved after the test for review unless -RemoveWorkingDir is passed.
run-tests — covers bin/test.ps1 for in-repo unit, integration, E2E,
CLI, and PowerShell tests. Use that skill for development-time testing.test-production (this skill) — covers bin/test-production.ps1 for
release-time acceptance testing of the published artifact.