browse

Run a headless Chromium browser for automated QA testing and visual diffs.

Updated Dec 13, 2017

Search Tags:#automation #screenshots #diff #playwright #browser #headless #qa-testing

Ready to run

npx skills add https://github.com/dogeared/tnra --skill browse-dogeared

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/dogeared/tnra --skill browse-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates QA testing by providing a fast headless browser that can navigate URLs, interact with elements, verify page state, diff before/after actions, take annotated screenshots, test responsive layouts, and handle dialogs.

Core Features & Use Cases

Persistent headless Chromium with commands to navigate, interact, diff, capture screenshots, test forms, and assert element states.
Supports viewing diffs between pages, capturing annotated evidence for bug reports, and validating responsive layouts.
Useful in CI pipelines and local dogfooding to verify deployments and reproduce user flows with reproducible state.

Quick Start

Run a simple QA test by navigating to a URL and capturing a screenshot for evidence.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I automate headless browser QA testing for CI pipelines?▼

Headless browser QA testing automates navigation, interaction, and state checks in CI pipelines by driving a persistent headless Chromium instance. It executes regression tests, feature checks, and bug reproduction with reproducible state across runs.

Can I capture screenshots and visual diffs during automated browser testing?▼

Screenshots and visual diffs are captured during automated browser testing to provide annotated evidence for bug reports. The headless browser captures page states before and after actions, enabling precise visual comparisons for regression detection.

Does headless browser testing support interaction with forms and dialog handling?▼

Headless browser testing supports form interactions, dialog handling, and state preservation across runs. It executes interaction commands, asserts element states, and handles dialogs to validate user flows and reproduce complex site behaviors.

What is the best way to test responsive layouts with a headless browser?▼

Testing responsive layouts with a headless browser involves driving automated navigation across viewport configurations to verify page states. It validates responsive rendering and captures visual evidence for local dogfooding and deployment verification.

When should I use a headless browser for regression testing instead of manual checks?▼

A headless browser should be used for regression testing when you need reproducible state, automated visual diffs, and fast execution in CI pipelines. It replaces manual checks by automating navigation, interaction, and state assertion commands for consistent verification.