Map changed files to routes and run browser tests with screenshots.
npx skills add https://github.com/jikig-ai/soleur --skill test-browser-jikig-ai
Please help me install this Agent Skill. Skill: test-browser Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/test-browser Command: npx skills add https://github.com/jikig-ai/soleur --skill test-browser-jikig-ai
Automate end-to-end browser tests for PR-affected pages to verify UI changes across routes and ensure regressions are caught early.
Run end-to-end browser tests on pages affected by a PR or branch changes using the agent-browser CLI.
High-intent search queries and answers about installing and using this skill.
To automate end-to-end browser tests for PR changes, this Skill maps changed files to affected routes and launches tests against those pages. It uses the agent-browser CLI to capture screenshots and verify UI consistency across branch changes.
Mapping changed files to routes works by analyzing your PR or branch changes to identify affected web pages. The Skill then targets only those specific routes for e2e-testing, capturing screenshots to validate UI consistency without testing the entire application.
Yes, you need a local dev server and the agent-browser CLI to run browser test-automation on PR-affected pages. The Skill requires the server to serve the application routes and the CLI to execute the end-to-end tests and capture screenshots.
Yes, you can use screenshot-based validation to catch UI regressions in web applications. The Skill captures visual snapshots of PR-affected pages, allowing you to compare screenshots and verify UI consistency across branch changes early in development.
The best way to perform pr-testing on affected routes is by mapping changed files directly to their corresponding URLs. This approach limits e2e-testing to only modified pages, capturing screenshots for verification and ensuring regressions are caught without testing the whole app.
E2e-testing for branch changes requires the agent-browser CLI because it provides the browser automation needed to launch tests on PR-affected pages. The CLI interacts with your local dev server to navigate routes and capture screenshots for UI regression checking.
jaydubya818Run end-to-end browser tests on routes affected by a PR or branch.
NOMARJReview Sigil quarantined items and approve or reject them via CLI.
DataDogIdentify changed files and run affected test suites via scripts/run-tests.
gsarmaonlineAutomate full-page screenshots across viewports using Puppeteer or Playwright for frontend applications.
