test-browser

Name: test-browser
Availability: InStock
Author: Udecode

Execute end-to-end browser tests on pull request-affected pages using agent-browser CLI.

240|75|Updated Jul 13, 2023

Search Tags:#automation #testing #e2e #qa #browser #agent-browser

Ready to run

npx skills add https://github.com/udecode/plate-playground-template --skill test-browser-udecode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/udecode/plate-playground-template/tree/main/.codex/skills/test-browser
Command: npx skills add https://github.com/udecode/plate-playground-template --skill test-browser-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of running end-to-end browser tests on web pages that have been modified by a current pull request or branch, ensuring code changes don't introduce regressions.

Core Features & Use Cases

Automated Browser Testing: Executes tests using the agent-browser CLI to simulate user interactions and verify page integrity.
Targeted Testing: Identifies and tests only the pages affected by recent code changes, optimizing the testing process.
Use Case: After pushing changes to a feature branch, run this Skill to automatically test all user-facing components that might have been impacted, catching visual bugs or broken functionality before merging.

Quick Start

Run browser tests for the current branch's changes.

Frequently Asked Questions about test-browser

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

FAQPage Schema

How do I run end-to-end browser tests only on pages affected by a pull request?▼

You can run end-to-end browser tests on affected pages by using an automation skill that identifies modified components in a pull request and executes targeted tests via the agent-browser CLI. It navigates and snapshots pages to catch regressions before merging.

What is automated browser testing for modified web application components?▼

Automated browser testing for modified components simulates user interactions to verify page integrity after code changes. It uses the agent-browser CLI to automate navigation and interaction testing, ensuring recent updates do not introduce visual bugs or broken functionality.

Do I need a local development server to run automated browser tests?▼

Yes, you need a local development server running to execute automated browser tests. The testing process requires a live local environment to navigate affected pages and verify user-facing components using the agent-browser CLI.

How do I automate navigation and interaction testing for web application pages?▼

You automate navigation and interaction testing by executing the agent-browser CLI against your local development server. The automation skill handles snapshotting, interaction testing, and failure reporting for web application components impacted by your branch.

Can I target e2e tests to only the pages changed in a feature branch?▼

Yes, you can target e2e tests to only changed pages by identifying components affected by recent code changes. This targeted testing approach optimizes the process by verifying page integrity exclusively for modified web application pages.

Why should I use targeted browser testing instead of running full test suites?▼

Targeted browser testing optimizes the testing process by executing tests only on pages affected by recent code changes. This approach catches visual bugs and broken functionality faster than full suites by focusing solely on modified web application components.