Drive a headless browser to automate end-to-end web QA workflows.
npx skills add https://github.com/benrapport/Vote-Better --skill browse-benrapport
Please help me install this Agent Skill. Skill: browse Source: https://github.com/benrapport/Vote-Better/tree/main/.claude/skills/gstack/browse Command: npx skills add https://github.com/benrapport/Vote-Better --skill browse-benrapport
Web QA often requires manual, brittle testing; this Skill provides a fast headless browser to automate testing workflows.
Use the gstack browse skill to start a headless QA browser session and begin testing web pages.
High-intent search queries and answers about installing and using this skill.
You can automate web testing by driving a headless browser to navigate URLs, interact with elements, and verify page state. This automates end-to-end QA workflows for feature validation, regression testing, and bug reproduction across responsive layouts, forms, and dialogs.
Yes, you can capture annotated screenshots during UI testing. The headless browser allows you to verify page state, diff before and after actions, and capture screenshots to visually confirm functional requirements across responsive breakpoints.
To test responsive layouts, you drive a headless browser to load web pages across different breakpoints. This allows you to validate feature behavior, check forms, and verify that UI elements render correctly across various screen sizes during regression testing.
Yes, you can run deterministic test automation tasks by loading operational instructions from optional scripts, references, and assets defined alongside the skill. This ensures consistent execution of feature validation and bug reproduction workflows.
Headless QA testing reproduces bugs in forms and dialogs by automating a browser to interact with UI elements and verify page state. It drives end-to-end workflows to validate forms, uploads, and dialogs across responsive layouts.
Headless browser test automation focuses on functional validation and regression testing of web pages, forms, and dialogs. It executes deterministic tasks but relies on defined scripts, references, and assets to verify page state rather than visual user experience.
vnmoorthyDrive a Playwright-backed headless browser to navigate pages and verify UI state.
johannesfritzRun pytest or Playwright/vitest suites and report pass/fail results.
aporto-techAutomate QA testing and site dogfooding with a headless browser.
robit-manCompare screenshots and analyze pixel differences across browsers and viewports.
