browser-test

Estrelas66.991

Forks7.995

Atualizado17 de julho de 2026 às 03:06

UI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

ruvnet

ruvnet/ruflo

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·SOC 15-1253

SKILL.md

readonly

name	browser-test
description	UI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run
argument-hint	<url> [--screenshot] [--against <prior-session-id>]
allowed-tools	mcp__plugin_ruflo-core_ruflo__browser_open mcp__plugin_ruflo-core_ruflo__browser_click mcp__plugin_ruflo-core_ruflo__browser_fill mcp__plugin_ruflo-core_ruflo__browser_type mcp__plugin_ruflo-core_ruflo__browser_press mcp__plugin_ruflo-core_ruflo__browser_check mcp__plugin_ruflo-core_ruflo__browser_uncheck mcp__plugin_ruflo-core_ruflo__browser_select mcp__plugin_ruflo-core_ruflo__browser_hover mcp__plugin_ruflo-core_ruflo__browser_wait mcp__plugin_ruflo-core_ruflo__browser_screenshot mcp__plugin_ruflo-core_ruflo__browser_snapshot mcp__plugin_ruflo-core_ruflo__browser_get-text mcp__plugin_ruflo-core_ruflo__browser_get-title mcp__plugin_ruflo-core_ruflo__browser_get-url mcp__plugin_ruflo-core_ruflo__browser_get-value mcp__plugin_ruflo-core_ruflo__browser_eval mcp__plugin_ruflo-core_ruflo__browser_close mcp__plugin_ruflo-core_ruflo__browser_session-list mcp__plugin_ruflo-core_ruflo__aidefence_is_safe Bash Read Write

Browser Test

Automated UI testing. Now backed by a recorded RVF session container instead of an ephemeral run, so every test produces a replayable artifact.

When to use

Verifying UI functionality, user flows, or that frontend changes work in a real browser.
Producing a baseline session that future regressions can diff against.
Re-running a stored test session when CI fails (no need to re-author the test).

Steps

Record the test run by composing browser-record:
- Allocates an RVF container with --kind browser-session.
- Begins a ruvector trajectory.
Drive interactions — browser_open, browser_click, browser_fill, browser_type, browser_select. Each action emits a trajectory-step.
Wait for elements / network idle via browser_wait before assertions.
Validate with browser_get-text / browser_get-value / browser_get-title / browser_get-url. Validation outcomes go into findings.md inside the RVF container.
Screenshot before / after key interactions for visual regression. Filenames follow <step-id>.png.
Snapshot the accessibility tree at navigation boundaries.
End the session: trajectory-end --verdict pass|fail, rvf compact, AgentDB index in browser-sessions.
(Optional) Diff against --against <prior-session-id>: invoke browser-screenshot-diff to compare the new run with a baseline.

Navigation

browser_back / browser_forward for history navigation
browser_reload to refresh the page
browser_scroll to scroll to elements or coordinates

What changed from v0.1.0

The skill no longer ends with browser_close alone — it ends with the session-end protocol.
Selectors discovered during the test land in browser-selectors (host:intent), so the next test can find them by embedding similarity.
Validation outputs pass aidefence_is_safe before any LLM-facing summary; injection-flagged content is quarantined to findings.md.
The same skill, used in CI, now produces an artifact that /ruflo-browser replay can re-drive.

Tips

Use browser_wait before assertions to handle async rendering.
For visual regression, save the parent session id and pass --against <id> on the next run.
Use browser_eval for custom JavaScript assertions — but redact any returned strings via the aidefence_is_safe gate before logging.

Mais deste repositório

mesmo repositório

ruflo

ruvnet/ruflo

Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.

2026-08-0467.0k

agntcy-status

ruvnet/ruflo

Show AGNTCY/SLIM/CASA integration status — whether upstream AGNTCY packages are installed, which transport (local vs SLIM) is active, and whether CASA enforcement is enabled. Use when the user asks "is AGNTCY configured?", "show SLIM/CASA status", or "is AGNTCY/IOC integration active?".

2026-07-3167.0k

adr-create

ruvnet/ruflo

Create a new Architecture Decision Record with sequential numbering and AgentDB registration

2026-07-2967.0k

adr-index

ruvnet/ruflo

Build or rebuild the ADR index + dependency graph by running scripts/import.mjs (handles v3-style and plugin-style ADR formats; one Bash call vs hundreds of MCP round-trips)

2026-07-2967.0k

harness-genome

ruvnet/ruflo

7-section repo readiness report from `metaharness genome <path>`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).

2026-07-2967.0k

ruflo-status

ruvnet/ruflo

Diagnose Ruflo health, then report system, MCP server, and active-agent status without changing the installation

2026-07-2967.0k

Browser Test

Automated UI testing. Now backed by a recorded RVF session container instead of an ephemeral run, so every test produces a replayable artifact.

When to use

Verifying UI functionality, user flows, or that frontend changes work in a real browser.

Producing a baseline session that future regressions can diff against.

Re-running a stored test session when CI fails (no need to re-author the test).

Steps

Record the test run by composing browser-record:

Allocates an RVF container with --kind browser-session.
Begins a ruvector trajectory.

Drive interactions — browser_open, browser_click, browser_fill, browser_type, browser_select. Each action emits a trajectory-step.

Wait for elements / network idle via browser_wait before assertions.

Validate with browser_get-text / browser_get-value / browser_get-title / browser_get-url. Validation outcomes go into findings.md inside the RVF container.

Screenshot before / after key interactions for visual regression. Filenames follow <step-id>.png.

Snapshot the accessibility tree at navigation boundaries.

End the session: trajectory-end --verdict pass|fail, rvf compact, AgentDB index in browser-sessions.

(Optional) Diff against --against <prior-session-id>: invoke browser-screenshot-diff to compare the new run with a baseline.

Navigation

browser_back / browser_forward for history navigation

browser_reload to refresh the page

browser_scroll to scroll to elements or coordinates

What changed from v0.1.0

The skill no longer ends with browser_close alone — it ends with the session-end protocol.

Selectors discovered during the test land in browser-selectors (host:intent), so the next test can find them by embedding similarity.

Validation outputs pass aidefence_is_safe before any LLM-facing summary; injection-flagged content is quarantined to findings.md.

The same skill, used in CI, now produces an artifact that /ruflo-browser replay can re-drive.

Tips

Use browser_wait before assertions to handle async rendering.

For visual regression, save the parent session id and pass --against <id> on the next run.

Use browser_eval for custom JavaScript assertions — but redact any returned strings via the aidefence_is_safe gate before logging.