ce-test-browser

Automated browser testing for PR changes uses the agent-browser CLI to validate affected pages by providing a PR number or branch name. It maps modified files to testable routes, executing deterministic browser actions and capturing rendered content to reduce manual QA time.

Scope-aware browser testing detects modified files from PRs or branches and maps them to testable routes to focus validation. This ensures automated end-to-end tests only target pages affected by recent code changes, increasing test coverage efficiency.

Yes, automated browser tests support configurable execution with both headed and headless modes. Headed mode enables human verification steps for sensitive flows, while port management and route coverage mapping ensure structured result reporting across PR-affected pages.

End-to-end browser testing handles port management automatically as part of its execution configuration. It fulfills requirements for prerequisites and port handling, allowing the agent-browser CLI to open pages, interact with elements, and validate changes across branches or PRs.

The best way to validate route coverage mapping for branch changes is using scope-aware testing that detects modified files and maps them to testable routes. This focuses automated browser validation on affected pages and generates structured result reporting.

Yes, automated browser testing is applicable when validating changes across both PRs and branches. You provide a branch name instead of a PR number, and the agent-browser CLI derives the test scope and maps modified files to routes for validation.