test-browser

Automate end-to-end browser testing of PR- or branch-affected pages.

6|Updated Jan 29, 2023

Search Tags:#automation #testing #qa #pr #browser #selenium #ci

Ready to run

npx skills add https://github.com/rethinkhealth/glion --skill test-browser-rethinkhealth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/test-browser
Command: npx skills add https://github.com/rethinkhealth/glion --skill test-browser-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables automated browser-based testing for pages affected by a PR or branch, ensuring UI changes render as expected before merging.

Core Features & Use Cases

End-to-end browser automation to open pages, interact with elements, and verify rendered content.
Scope tests to changed routes by analyzing PR diffs or specified branch changes.
Use case: when a PR touches multiple views, quickly validate layout, forms, and navigation across affected pages.

Quick Start

Run browser tests on pages changed by the current PR or branch using the test-browser skill.

Frequently Asked Questions about test-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run automated browser tests only on pages affected by a PR?▼

Automated browser testing for PR-affected pages analyzes code diffs to scope test execution, opening changed routes to interact with UI elements and verify rendered content before merging.

Can I scope end-to-end UI tests to specific branch changes instead of the full suite?▼

Yes, end-to-end browser automation can be scoped to specific branch changes, analyzing diffs to validate layout, forms, and navigation only across affected pages rather than running the full test suite.

What is the best way to verify UI changes render correctly before merging a pull request?▼

Browser-based testing of PR-affected pages verifies UI changes by orchestrating browser automation to open pages, interact with elements, and capture state, ensuring new code changes render as expected.

Does automated browser testing handle server verification and port detection during setup?▼

Automated browser testing satisfies workflow prerequisites including environment setup, port detection, and server verification before orchestrating the CLI to interact with UI elements and capture state.

How do browser tests capture state and interact with elements on changed routes?▼

Browser tests orchestrate a CLI to open pages, interact with UI elements, and capture state, applying scoped test execution to code changes in PRs or branches for visual checks.

When should I use scoped browser testing instead of running the entire test suite?▼

Scoped browser testing is ideal when a PR touches multiple views and you need to quickly validate layout, forms, and navigation across affected pages without executing the full test suite.