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.