Automate end-to-end browser tests for pages changed by a PR or branch.
npx skills add https://github.com/The-Rabak/naysmith --skill test-browser-the-rabak
Please help me install this Agent Skill. Skill: test-browser Source: https://github.com/The-Rabak/naysmith/tree/main/.github/skills/test-browser Command: npx skills add https://github.com/The-Rabak/naysmith --skill test-browser-the-rabak
This skill reduces manual QA effort by automatically running browser tests on pages changed by a PR or branch, catching UI regressions early.
Run the test-browser command on your PR or branch to begin browser-based validation.
High-intent search queries and answers about installing and using this skill.
You can automate end-to-end browser testing for pages changed by a PR by scoping test execution to modified routes and components, catching UI regressions early without manual QA effort.
Yes, a local development server is required to run the automated browser tests and generate visual snapshots that verify UI behavior on the modified routes of your application.
Yes, browser tests support both headed and headless modes, allowing you to balance visual debugging during test failures with execution speed for automated PR testing workflows.
Automated UI regression testing for modified routes works by using the agent-browser CLI to execute end-to-end tests on changed pages, generating test results and visual snapshots to verify UI behavior.
The best way to catch UI regressions early is to automate end-to-end browser tests scoped to affected pages, generating visual snapshots to verify UI behavior on modified routes quickly.
Ouro-labsAutomate browser testing of web pages changed in pull requests or branches using agent-browser CLI.
somachakCompare current UI and data outputs against stored golden snapshots to detect regressions.
DieStokExecute end-to-end browser tests on pages modified by a PR or branch.
gzp79Validate Svelte component props, state, and UI interactions with Vitest.
