ce-test-browser
Run browser tests for pages affected by the current branch or PR
by everyincFree
Description
ce-test-browser runs end-to-end browser tests on the pages affected by a pull request or branch. It uses the best approved browser driver available in the current harness. Each affected route is reported as Pass, Fail or Skip, and every Skip carries its reason. If a preflight problem stops testing before any route can be exercised, the skill reports the blocker and what would be needed to continue instead. Its modes and driver policy define which browser tools may be used. It is useful for checking that a change works in the browser before it is handed off or merged, without writing a test suite for each route by hand. The skill is part of the compound-engineering plugin by Every and is listed on skills.sh as free.…
Highlights
- Browser tests for pages affected by a branch or PR
- Each route reported as Pass, Fail or Skip with reasons
- Uses the best approved browser driver in the harness
- Reports blockers when testing cannot start
Ratings & Reviews
No ratings yet
Be the first to rate ce-test-browser.
People also visit
gh-issues
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs
ce-test-browser FAQ
What does ce-test-browser test?
The pages affected by the current branch or pull request.
What results does it give?
Pass, Fail or Skip for each affected route, with a reason for every Skip.
What if testing cannot start?
The skill reports the blocker and what would be needed.
How do I install it?
Run npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-test-browser in your terminal.
Is it free?
The listing shows the skill as free.
What are the best ce-test-browser alternatives?
Popular alternatives to ce-test-browser include ce-code-review, ce-commit-push-pr and ce-resolve-pr-feedback. See all ce-test-browser alternatives