ce-test-browser

To automate browser tests for PR-affected pages, you map changed files to routes and validate UI flows using the agent-browser CLI against a running dev server. This verifies rendering and interactions without manual checks.

Automated end-to-end browser testing for changed routes validates that pages affected by a branch render correctly and interactions work. It scopes tests to only modified files mapped to routes for efficient verification.

Yes, a running development server is required to run automated browser tests on PR pages. You also need the agent-browser CLI and a test plan that maps changed files to routes to execute the verification.

Yes, you can run headless browser tests in CI pipelines for changed UI flows. The testing tool supports both headless mode for CI pipelines and headed mode for local testing with interactive snapshots.

The best way to scope end-to-end tests to changed pages is by using a test plan that maps changed files to routes. This ensures the browser tests cover only the affected UI flows rather than the entire application.

Automated browser tests may not cover correct PR-affected routes if the test plan mapping changed files to routes is misconfigured. You must accurately map modified files to their corresponding routes before execution.