test-browser

Execute browser tests on web pages affected by code changes.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/kenhia/kdeskdash --skill test-browser-kenhia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/kenhia/kdeskdash/tree/main/.github/skills/test-browser
Command: npx skills add https://github.com/kenhia/kdeskdash --skill test-browser-kenhia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates and executes end-to-end browser tests, enabling quick feedback on the impact of code changes on web applications.

Core Features & Use Cases

  • Automated Tests: Run tests automatically on affected pages when a PR or branch is changed.
  • Headed/Headless Execution: Choose to view tests in a visible browser window or run them headlessly for faster execution.
  • Scope Definition: Determines which files to test based on code changes, providing specific test cases.
  • Server and Port Detection: Handles server port detection and verification for accurate test execution.
  • Test Execution and Verification: Interacts with the browser to navigate, interact with elements, capture snapshots, and verify critical elements and interactions.
  • Error Handling and Reporting: Provides detailed logs on test results, highlighting any failures or issues that need attention.

Quick Start

Run tests on the current branch by executing the skill command: /test-browser current.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I automate browser tests for a specific pull request?

To automate browser tests for a pull request, execute the test automation skill via CLI. It identifies web pages affected by code changes, runs targeted tests, and reports successes or failures.

What is automated browser testing for code changes?

Automated browser testing for code changes executes end-to-end tests on affected web pages. It detects server ports, verifies page interactivity, captures snapshots, and provides detailed feedback on test results.

Can I run headless browser tests for faster CI/CD integration?

Yes, you can run headless browser tests for faster CI/CD integration. The skill supports both headed and headless execution modes, allowing you to run tests invisibly for quicker automated testing.

How does automated testing handle server port detection?

Automated testing handles server port detection by verifying test environments before execution. It automatically detects the correct server port to ensure accurate browser test execution and page interaction verification.

How do I review test automation failures in my web application?

To review test automation failures, check the detailed logs generated by the skill. It provides error handling and reporting features that highlight specific test failures and issues requiring attention.

Does test-browser work with branch-specific changes?

Yes, test-browser supports PR-specific or branch-specific tests. By running the CLI command, it defines the test scope based on code changes and identifies which specific files require testing.