Runs automated browser tests on pages changed by a PR or branch.
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill test-browser-bradliebs
Please help me install this Agent Skill. Skill: test-browser Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/test-browser Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill test-browser-bradliebs
Validate that pages affected by a PR or branch work correctly by running automated end-to-end browser tests, reducing regressions before merging.
Run test-browser on your current branch or a PR to validate affected pages with the agent-browser CLI.
High-intent search queries and answers about installing and using this skill.
Automated browser testing for PRs works by mapping changed files to testable routes, discovering the dev server port, and executing end-to-end validation via a dedicated CLI. This generates a deterministic test plan with snapshots and interactions to ensure UI integrity.
End-to-end validation for feature branches is the process of executing automated browser tests on pages affected by code changes to reduce regressions. It determines the dev server port, maps changed files to routes, and runs browser automation to validate UI integrity before merging.
Yes, you can use this browser testing approach in CI workflows to quickly validate PRs, feature branches, or deployment previews. It identifies changed pages and applies deterministic browser automation to ensure affected routes work correctly before merging.
Yes, executing browser tests requires a running dev server. The testing process includes requirements for server setup and port discovery to map changed files to testable routes, ensuring the agent-browser CLI can perform deterministic interactions and snapshots.
Route mapping for automated browser tests works by identifying changed files in a PR or branch and mapping them to testable routes. This determines the dev server port and generates a deterministic test plan to guide the browser automation CLI in validating affected pages.
Running browser tests only on changed pages focuses validation strictly on affected routes mapped from modified files. It does not test the entire application UI, meaning regressions in untouched pages or global state changes outside the mapped route plan will not be detected.
jaydubya818Run end-to-end browser tests on routes affected by a PR or branch.
mazicimertGenerate snapshot test boilerplate and CI configuration for SwiftUI projects.
Jason-Clark-FGValidate UI changes on feature branches with Playwright end-to-end tests.
aarushlohitRun Playwright end-to-end browser tests across multiple environments.
