Agent skill

Run Tests

by platonai in platonai/Browser4

Discovers and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production acceptance).

Apache-2.0Auto-check passedTesting & QA

Install Run Tests

skills CLI
$ npx skills add platonai/Browser4 --skill run-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install platonai/Browser4 run-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coworker/skills/run-tests .claude/skills/run-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-tests
GitHub stars
1.2k
Token cost
~1.9k tokens
SKILL.md length
649 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
Apache-2.0

At a glance

Discovers and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production acceptance).

  • Works in 11 steps: Creates an isolated working directory… → Cleans any pre-existing global… → Installs the latest CLI via the remote… → …
  • Tasks that involve End-to-end testing
  • SKILL.md covers When to Use, How It Works, Usage and Test Session, plus 1 more section
  • Calls cargo

What it does

Run Tests is an agent skill from platonai/Browser4. Discovers and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production acceptance). Use when asked to run, check, or verify tests.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing and Test generation. It works with PowerShell. The repository describes itself as: Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve End-to-end testing
  • Tasks that involve Test generation

Example prompts

  • “Use the run-tests skill to discover and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production…”
  • “/run-tests”

Requirements

  • Pre-approved tools (allowed-tools): Bash(pwsh:*), Bash(./bin/test.ps1:*)

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Creates an isolated working directory (default: system temp + random suffix)
  2. Cleans any pre-existing global browser4-cli installation
  3. Installs the latest CLI via the remote bootstrap script (unmodified)
  4. Verifies the CLI is on PATH after install (fails if the install script is broken)
  5. Smoke-tests: --help, --version, config --help, agent-run --help, invalid command
  6. Cold-starts the browser server (open), verifies health endpoint responds
  7. Measures warm-start latency vs cold-start (cycle 2)
  8. Shuts down the server (close-all, kill-all), verifies it's unreachable
  9. Uninstalls and verifies runtime data is removed
  10. Repeats the install cycle to verify idempotency
  11. (With -Stress) Runs multi-scenarios.ps1 against the global CLI

What it can do on your machine

Read from SKILL.md and the folder at commit 0fdba82. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(pwsh:*)
    • Bash(./bin/test.ps1:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Tests loads about 1.9k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 649 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from platonai/Browser4 at commit 0fdba82, republished under its Apache-2.0 licence (© platonai). 649 words, ~1,924 tokens.

Download SKILL.mdSave it as .claude/skills/run-tests/SKILL.md (or your agent's skills folder).
name
run-tests
description
Discovers and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production acceptance). Use when asked to run, check, or verify tests.
allowed-tools
Bash(pwsh:*), Bash(./bin/test.ps1:*)
title
Run Tests — Execute Browser4 test suites via bin/test.ps1

Run Tests

Two test entrypoints:

  • bin/test.ps1 — unified test orchestrator for the Browser4 monorepo. Supports Maven tests, Rust CLI tests, PowerShell *.tests.ps1 files, real-world scenario agent evaluations, and mock-server launch.

  • bin/test-production.ps1 — acceptance test for the latest production release of browser4-cli. Downloads, installs, exercises, uninstalls, and re-installs the global CLI from the public OSS distribution channel.

When to Use

  • "run the tests"
  • "run fast / unit tests"
  • "run integration / it tests"
  • "run e2e tests"
  • "run cli tests"
  • "run all PowerShell tests"
  • "run real-world scenarios"
  • "check what tests would run" (-DryRun / -Show)
  • "resume failed tests"
  • "launch mock server"
  • "run production acceptance test"
  • "acceptance test the latest release"

How It Works

bin/test.ps1 buckets test-type arguments into dispatch categories (Maven, CLI, PowerShell, RWS, server) and runs each in sequence. The script must be invoked from the repository root (it Set-Locations there automatically).

Test results are persisted per invocation to .test-sessions/<session-id>/test-session.json (see bin/common/test-session.psm1). Pass -NoSession to skip persistence or -SessionPath to write to a custom location.

Usage

bash
./bin/test.ps1 [OPTIONS] [TEST-TYPES...] [EXTRA-ARGS...]
Options
FlagDescription
-DryRunCompile only (test-compile), do not run tests
-ShowPrint the final command, do not execute anything
-NoSessionSkip persisting test results to .test-sessions/
-SessionPath <path>Custom path for the test-session JSON file
Test Types
TypeCategoryDescription
fastMavenFast unit tests
itMavenIntegration tests (-DrunITs=true)
e2eMavenEnd-to-end tests (-DrunE2ETests=true)
restMavenREST module tests (-DrunRestTests=true)
skillsMavenSkills-focused agentic tests (browser4-agentic)
mcpMavenMCP-focused agentic tests (browser4-agentic)
mainMavenAll Browser4 main tests: fast + it + e2e + rest
cliCLIRust Browser4 CLI tests (cargo test --test e2e). Alias: browser4-cli
psPowerShellAll *.tests.ps1 files in the project
resumeMavenResume from the last failed module (-rf)
mock-siteServerLaunch MockSiteBoot (aliases: server, mocksite)
rwsRWSReal-world scenario agent evaluations. Bare rws shows help; pass --scenarios or --task to run.
RWS Flags (accepted after rws)
FlagDescription
--scenarios [names...]Run agent-scenario tasks (requires claude or kimi)
--task <file>Run a single task file
--productionUse installed browser4-cli instead of cargo run
--fail-fastStop after the first failing scenario
--listList discovered scenarios, don't run
--silentSuppress agent output
--skip-version-checkSkip browser4-cli version check
--timeout <minutes>Per-task timeout (default: no timeout)
Examples
bash
# Run fast unit tests
./bin/test.ps1 fast

# Show the Maven command without executing
./bin/test.ps1 -DryRun fast

# Run integration tests with extra Maven args
./bin/test.ps1 it -pl browser4-core

# Run end-to-end tests
./bin/test.ps1 e2e

# Run CLI tests (Rust cargo test)
./bin/test.ps1 cli

# Pass extra cargo test args to CLI tests
./bin/test.ps1 cli -- --help

# Run all PowerShell test files (+ the skills/ document conformance check)
./bin/test.ps1 ps

# Run all PS tests quietly
./bin/test.ps1 ps -Quiet

# Run all main tests together
./bin/test.ps1 main

# Run fast tests and PS tests together
./bin/test.ps1 fast ps

# Run fast tests without persisting session
./bin/test.ps1 -NoSession fast

# Write session to a custom path
./bin/test.ps1 -SessionPath out/session.json ps

# Preview what tests would be run
./bin/test.ps1 -Show main

# Resume from the last failed Maven module
./bin/test.ps1 resume

# Launch the mock server
./bin/test.ps1 mock-site -Dmock.site.port=18080

# Run all real-world scenarios
./bin/test.ps1 rws --scenarios

# Run a specific scenario
./bin/test.ps1 rws --scenarios amazon

# Run scenarios against installed production CLI
./bin/test.ps1 rws --scenarios --production

# List discovered scenarios
./bin/test.ps1 rws --scenarios --list

# Run a single task file directly
./bin/test.ps1 rws --task tasks/real-world/generic/amazon.md

# Run scenarios with 30-minute per-task timeout
./bin/test.ps1 rws --scenarios --timeout 30

Test Session

After each invocation, results are persisted to .test-sessions/<session-id>/test-session.json. To inspect the latest session:

bash
ls -t .test-sessions/*/test-session.json | head -1 | xargs cat

The session records the last status, log paths, per-file results (for ps), system environment, and a rolling 5-entry history per test type. Pass -NoSession to skip persistence, or -SessionPath <path> to write to a custom location.

Show full SKILL.md (241 more words)Show less

Production Acceptance Test

bin/test-production.ps1 simulates a real end user's journey with the published browser4-cli release. It is designed to be run in CI or locally before tagging a release.

Safe default

Running with no arguments shows help (safe default):

bash
./bin/test-production.ps1
Options
FlagDescription
-WorkingDir <path>Working directory for temporary artifacts (default: random subdir under system temp)
-StressEnable the multi-scenario stress suite (opt-in)
-MultiScenariosIterations <n>Iterations for the multi-scenario suite (default: 1, only with -Stress)
-RemoveWorkingDirDelete the working directory on exit (default: preserved for review)
What it tests
  1. Creates an isolated working directory (default: system temp + random suffix)
  2. Cleans any pre-existing global browser4-cli installation
  3. Installs the latest CLI via the remote bootstrap script (unmodified)
  4. Verifies the CLI is on PATH after install (fails if the install script is broken)
  5. Smoke-tests: --help, --version, config --help, agent-run --help, invalid command
  6. Cold-starts the browser server (open), verifies health endpoint responds
  7. Measures warm-start latency vs cold-start (cycle 2)
  8. Shuts down the server (close-all, kill-all), verifies it's unreachable
  9. Uninstalls and verifies runtime data is removed
  10. Repeats the install cycle to verify idempotency
  11. (With -Stress) Runs multi-scenarios.ps1 against the global CLI
Key principle

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.

Examples
bash
# Show help (no arguments = safe default)
./bin/test-production.ps1

# Run the full acceptance test
./bin/test-production.ps1 -Stress

# Production CI: stress test with multiple iterations, clean up afterward
./bin/test-production.ps1 -Stress -MultiScenariosIterations 3 -RemoveWorkingDir

# Use a specific working directory
./bin/test-production.ps1 -WorkingDir /tmp/my-acceptance-test

© platonai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in coworker/skills/run-tests of platonai/Browser4.

Open the folder on GitHubat commit 0fdba82

Compare with similar skills

Run Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Tests this skillplatonai/Browser41.2k—~1.9kAutomated safety check: PassApache-2.0
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
Engine E2Ewix/react-native-navigation13k—~1.1kAutomated safety check: PassMIT
Senior QAnicepkg/auto-company1923 repos~1.1kAutomated safety check: NotesNone
Explore Feature E2E Testcomet-ml/opik22k—~3.4kAutomated safety check: PassApache-2.0
Kane CLI Browser TestingLambdaTest/kane-cli247—~8.4kAutomated safety check: PassApache-2.0

Similar skills

  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Engine E2E

    wix/react-native-navigation

    Official

    Run Wix Engine (mobile-apps-engine) iOS E2E tests locally to validate RNN changes.

    13k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Senior QA

    nicepkg/auto-company

    Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.

    192 GitHub starsUsed in 3 repos~1.1k tokens
    Testing & QAAuto-check: notes
  • Turns a code change into one committed, passing Playwright end-to-end spec by resolving the change scope and handing authoring to a companion skill.

    22k GitHub stars~3.4k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Kane CLI Browser Testing

    LambdaTest/kane-cli

    Drives a real browser through the kane-cli tool and designs requirement-linked test suites from a PRD or a plain description, with mobile and cloud-grid runs.

    247 GitHub stars~8.4k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Run E2E Test

    kubernetes-sigs/cloud-provider-azure

    Official

    Parse a Go e2e test from tests/e2e/, translate each step to kubectl and az CLI commands, and interactively replay the test against a live cluster.

    294 GitHub stars~3.8k tokensUpdated today
    Testing & QAAuto-check passed

More from platonai/Browser4

All 17 skills in this repo
  • Data Validation

    platonai/Browser4

    Validates data against common and custom rules (required fields, formats, ranges).

    1.2k GitHub stars~896 tokensUpdated today
    Auto-check passed
  • Form Filling

    platonai/Browser4

    Automatically fills web forms using provided field data and can optionally submit the form.

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Web Scraping

    platonai/Browser4

    Extracts data from web pages using browser automation and CSS/JavaScript selectors.

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Organize Task Files

    platonai/Browser4

    Lists, pairs, deduplicates, and moves task files across the Coworker task state machine (0draft → 6git-pushed).

    1.2k GitHub stars~801 tokensUpdated today
    Auto-check passed
  • Task Token Usage

    platonai/Browser4

    Analyzes Claude Code session traces (JSONL) and draft task files to report token usage per task.

    1.2k GitHub stars~701 tokensUpdated today
    Auto-check passed
  • Weather

    platonai/Browser4

    Fetches current weather conditions and a 7-day forecast for a requested location using Open-Meteo geocoding and forecast APIs.

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Run Tests

What does Run Tests do?

Discovers and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production acceptance). Run Tests is an agent skill from platonai/Browser4. Discovers and runs Browser4 test suites (unit, integration, E2E, CLI, PowerShell, real-world scenarios, production acceptance).

When should I use Run Tests?

Run Tests fits situations like: tasks that involve End-to-end testing; tasks that involve Test generation.

How do I install Run Tests in Claude Code?

Run `npx skills add platonai/Browser4 --skill run-tests -a claude-code`. Or copy the skill folder (coworker/skills/run-tests in platonai/Browser4) into .claude/skills/run-tests in your project. Claude Code loads it when a task matches its description.

How do I install Run Tests in Codex?

Run `npx skills add platonai/Browser4 --skill run-tests -a codex`. Or copy the skill folder (coworker/skills/run-tests in platonai/Browser4) into .agents/skills/run-tests in your project. Codex loads it when a task matches its description.

Can I use Run Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add platonai/Browser4 --skill run-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-tests, .gemini/skills/run-tests, .github/skills/run-tests and .opencode/skills/run-tests in your project.

What does Run Tests need to run?

Going by SKILL.md and its folder, Run Tests needs the command-line tools its instructions call (cargo). Its frontmatter pre-approves these tools: Bash(pwsh:*), Bash(./bin/test.ps1:*).

Does Run Tests access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Run Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run Tests use?

Run Tests is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Tests use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Tests?

Skills that share tags, products or a category with Run Tests: Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars), Engine E2E (wix/react-native-navigation, 13k stars), Senior QA (nicepkg/auto-company, 192 stars) and Explore Feature E2E Test (comet-ml/opik, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Tests?

platonai (a GitHub user) maintains it in platonai/Browser4, which has 1,152 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: platonai/Browser4 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.