se-test-browser

You can automate end-to-end browser testing for UI changes by running a skill that uses the agent-browser CLI to map modified files to testable routes and verify key UI elements in the current PR or branch. It captures screenshots to validate visual and functional correctness before merging.

Automated UI validation for modified routes is the process of mapping changed files to affected pages and executing browser tests to ensure updated interfaces render and interact correctly. This skill automates that mapping and testing process using the agent-browser CLI.

Yes, you need a local dev server running to execute browser tests on a branch, along with the agent-browser CLI installed and a PR or branch context. You can optionally specify the server port using the --port flag.

Yes, you can run headless browser tests for PR UI changes to prioritize execution speed, or switch to headed execution for visual observability. This skill supports both modes via the agent-browser CLI.

To map changed files to testable pages for UI regression testing, this skill analyzes the touched files in your current PR or branch context, identifies the corresponding routes, and executes browser tests on those specific pages.

Limitations of automated branch browser testing include the requirement to have agent-browser installed, an active local dev server, and a PR or branch context. Without these prerequisites, the skill cannot execute the UI validation tests.