Automate browser-based QA testing with persistent headless Chromium.
npx skills add https://github.com/pistosmin/base-one --skill browse-pistosmin
Please help me install this Agent Skill. Skill: browse Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/browse Command: npx skills add https://github.com/pistosmin/base-one --skill browse-pistosmin
Automates browser-based QA testing using a persistent headless Chromium. Ideal for feature verification, deployment checks, and bug reproduction by navigating URLs, interacting with elements, validating state, and capturing annotated evidence. Requires Playwright-based automation, supports screenshots, diffs, form tests, responsive checks, and dialog handling, with deterministic ~100ms per-command latency.
Start by opening a URL and asking the browser to perform a quick sanity check, such as loading the page and taking a screenshot for evidence.
High-intent search queries and answers about installing and using this skill.
Automate headless browser QA testing by using a persistent headless Chromium to navigate URLs, interact with elements, and verify page state. This approach captures annotated screenshots as evidence for feature verification and deployment checks.
Yes, persistent browser state maintains cookies, tabs, and login sessions across calls for end-to-end QA. This allows continuous automated testing flows without needing to re-authenticate or rebuild session context between interactions.
The best way to capture annotated screenshots during Playwright automation is to navigate the target URL and trigger a sanity check. The browser captures visual evidence, supporting diffs and responsive layout validation during automated flows.
Yes, you need Bun and Perl installed as dependencies to run these automated browser testing scripts. They provide the necessary runtime environment to execute the Playwright-based automation commands with deterministic latency.
Test forms and handle dialogs in a headless Chromium environment by interacting with elements and asserting their states during automated flows. The browser supports form tests, uploads, and dialog handling with deterministic latency.
Automated QA testing should have deterministic latency around 100ms per command. If latency is higher, it may indicate an improperly configured persistent headless Chromium environment or issues with the underlying Playwright-based automation scripts.
XinheLIUOperate a persistent headless Chromium browser for QA testing and site dogfooding.
nhattran998Drive a headless browser to load URLs, interact with elements, and capture page state.
ShmurdocAutomate headless browser testing and capture annotated screenshots for bug reports.
cloudofgeorgeDrive a headless browser to automate QA testing and capture screenshots.
