ce-test-browser

Run end-to-end browser tests on modified PR pages by applying automated validations to routes derived from changed files. The tool manages dev server ports and captures snapshots to verify UI behavior before merge.

Automating UI validation for branches is best handled by targeting only the pages affected by code changes. This routes tests based on modified files, capturing snapshots to catch regressions without manually checking every page.

Yes, you can execute headless browser tests in a pipeline. The skill supports configurable runs in headed or headless modes and includes port management specifically designed for pipeline and local development environments.

Yes, the browser testing tool manages dev server ports automatically. It handles port configuration in both pipeline and manual modes, ensuring automated end-to-end tests run without network conflicts during local development or CI.

Catch UI regressions across affected PR routes by running automated browser tests that derive test paths from changed files. The tool snapshots and verifies key UI elements on modified pages to ensure interface integrity before merging.

You need to run end-to-end browser tests on branch changes when manually validating multiple pages becomes error-prone. Automating this process ensures UI integrity and catches visual regressions before merging code changes.