browse

Automates web-app testing through a CLI-driven virtual browser interface.

2|2|Updated Dec 1, 2024
One-click install
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill browse-yaugourt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/browse
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill browse-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

QA teams and developers want fast, repeatable browser tests without manual steps. This skill provides a fast headless browser to navigate URLs, interact with elements, verify page state, and capture evidence for bugs.

Core Features & Use Cases

  • Fast navigation and interaction: navigate any URL, click elements, fill fields, and verify UI states.
  • Evidence-driven QA: diff before/after actions and generate annotated screenshots for bug reports.
  • Responsive testing and forms: test layouts across viewports and validate forms and uploads automatically.
  • Deterministic, scriptable workflows: command-level execution with predictable timing and logging.

Quick Start

Navigate to a URL with goto <url> and start testing with snapshot or screenshot commands.

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 testing for feature verification?

Headless browser QA automates feature verification by controlling a browser to navigate URLs, interact with elements, and validate UI states deterministically. You execute scriptable workflows to run repeatable test steps rapidly without manual intervention.

Can I capture annotated screenshots during web automation tests?

Yes, web automation tests can generate annotated screenshots as evidence for bug reports. The headless browser captures visual diffs before and after interaction actions, providing deterministic logging and visual proof for QA validation.

What is the best way to validate responsive layouts across different viewports?

Validating responsive layouts involves testing UI rendering across multiple viewports using a headless browser. The automation checks page states and layout shifts deterministically, ensuring consistent rendering without manual visual inspection for each screen size.

Does this headless browser approach work for form validation and file uploads?

Yes, the headless browser approach handles form validation and file uploads by scripting element interactions like filling fields and submitting data. It verifies form completion through deterministic commands with predictable execution timing and logging.

How do I script deterministic user-flow dogfooding for deployment validation?

User-flow dogfooding scripts deterministic browser commands to navigate and interact with pages for deployment validation. It coordinates navigation, element interaction, state validation, and logging with predictable timing and safe defaults to verify deployments.

Are there limitations when using headless browser automation for QA testing?

Headless browser automation limitations include reliance on deterministic commands with safe defaults, meaning tests require predictable timing and scriptable workflows. Complex non-deterministic page states may challenge automated element interaction and validation logging.