Browser Test
Skill Verified ActiveUI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run
To provide a reliable and replayable method for automated UI testing, ensuring frontend changes function correctly and producing tangible artifacts for regression analysis.
Features
- Composes browser recording (capture) with browser replay (verify)
- Produces replayable RVF artifacts instead of ephemeral runs
- Supports interaction via browser_open, browser_click, browser_fill, etc.
- Includes validation steps using browser_get-* tools
- Facilitates visual regression testing with screenshots and diffing
Use Cases
- Verifying UI functionality and user flows in a real browser
- Producing a baseline session for future regression testing
- Re-running stored test sessions when CI fails, without re-authoring tests
Non-Goals
- Performing backend API testing
- Unit testing individual components
- Generating test cases from scratch without user interaction
Workflow
- Record test run using browser-record
- Drive interactions with browser_* tools
- Wait for elements/network idle via browser_wait
- Validate outcomes with browser_get-* tools
- Screenshot before/after key interactions
- Snapshot accessibility tree
- End session with trajectory-end and rvf compact
- Optionally, diff against a prior session ID
Practices
- UI Testing
- Regression Testing
- Automated Verification
Prerequisites
- Claude Code
- Browser interaction tools (e.g., Playwright)
Scope
- info:Tool surface sizeThe skill exposes a large number of specific browser interaction tools, exceeding the ideal range but still manageable within the domain.
Installation
First, add the marketplace
/plugin marketplace add ruvnet/ruflo/plugin install ruflo-browser@rufloQuality Score
VerifiedTrust Signals
Similar Extensions
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Telegram Crabbox E2e Proof
100Use when reviewing, reproducing, or proving OpenClaw Telegram behavior with a real Telegram user on Crabbox, including PR review workflows that need an agent-controlled Telegram Desktop recording, TDLib user-driver commands, Convex-leased credentials, WebVNC observation, and motion-trimmed artifacts.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Agent Browser
100Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Vue Testing Best Practices
100Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.
Develop Web Game
100Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text.