test-production

Acceptance-tests the published browser4-cli release by installing, exercising, and uninstalling it.

1.1k|151|Updated Mar 12, 2018
One-click install
npx skills add https://github.com/platonai/Browser4 --skill test-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-production
Source: https://github.com/platonai/Browser4/tree/main/coworker/skills/test-production
Command: npx skills add https://github.com/platonai/Browser4 --skill test-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before tagging a release, teams need confidence that the published browser4-cli artifact actually works for real end users. This Skill runs an acceptance test that downloads, installs, exercises, uninstalls, and re-installs the CLI from public distribution channels, catching broken install scripts or packaging issues that in-repo tests would miss.

Core Features & Use Cases

  • End-user simulation: Installs the CLI via the unmodified remote bootstrap script, smoke-tests commands, cold-starts the browser server, and verifies uninstall cleanup.
  • Multi-channel release verification: Queries GitHub Releases, npm registry, Aliyun OSS CDN, and mirrors to confirm all distribution channels are reachable.
  • Optional stress suite: Runs multi-scenario stress tests with configurable iterations against the globally installed CLI.
  • Use Case: Before tagging v4.12.0, run the acceptance test with stress enabled to verify the prerelease candidate installs cleanly and passes all scenarios in an isolated sandbox.

Quick Start

Ask the agent to run the production acceptance test for the latest browser4-cli release with the stress suite enabled.

Frequently Asked Questions about test-production

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

FAQPage Schema
How do I acceptance-test a browser4-cli release before tagging?

Run bin/test-production.ps1, which downloads and installs the published CLI, smoke-tests its commands, starts and stops the browser server, then uninstalls and re-installs it. Add -Stress for the multi-scenario stress suite.

What is the difference between test.ps1 and test-production.ps1?

test.ps1 (covered by the run-tests skill) runs in-repo unit, integration, E2E, and CLI tests against source code. test-production.ps1 tests the released artifact from public distribution channels, simulating a real end user.

Can I test a specific prerelease version of browser4-cli?

Yes, pass the -Version flag with a tag such as v4.12.0-rc.1 to test a specific prerelease, or a stable tag like v4.11.0. Without the flag, the latest stable release is tested.

Does the production acceptance test modify my local browser4 config?

No. The test routes all state and runtime data into an isolated working directory using BROWSER4_CLI_STATE_DIR and BROWSER4_RUNTIME_DIR. Your real ~/.browser4 is only read to copy config into the sandbox during the second install cycle.

Why does the production acceptance test fail when install scripts need manual fixes?

The test deliberately acts like a real end user and never patches install scripts, creates missing symlinks, or cleans up manually. If such workarounds are needed, the test fails because real users would hit the same broken behavior.