browser-test

Execute manual browser tests in Chrome with navigation, form interactions, and state verification.

2|Updated May 15, 2026

Search Tags:#UI testing #web automation #browser testing #feature verification #manual QA

Ready to run

npx skills add https://github.com/bdbch/ai-dotfiles --skill browser-test-bdbch

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill allows for manual testing of web features, enabling a QA engineer-like approach to verification by interacting with a browser environment.

Core Features & Use Cases

End-to-End Manual Testing: Navigate through web pages, perform actions, and verify behaviors just like a human QA engineer.
Test Scenario Execution: Follow user-provided steps to confirm feature functionality.
Error Reporting: Identify issues like navigation problems, UI errors, or broken interactive elements.
Use Case: Use this skill to ensure a new feature in a web application works correctly before releasing it to the public.

Quick Start

Start the browser-test skill to begin manual testing of your web feature by opening 'testpage.html' in Chrome and following the test scenario provided.

Frequently Asked Questions about browser-test

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

FAQPage Schema

How do I manually test web features in Chrome to simulate end-user interaction?▼

To manually test web features in Chrome, you can use a skill that opens a browser environment for end-user interaction simulation. It enables you to navigate pages, fill out forms, and verify UI state to reproduce bugs or check feature functionality.

Can I run automated UI regression checks with this browser testing approach?▼

No, you cannot run automated UI regression checks with this approach. It is designed exclusively for manual end-to-end testing, requiring a user to manually interact with the Chrome browser rather than executing automated testing scripts.

What is the best way to reproduce bugs and verify UI state during web automation?▼

The best way to reproduce bugs and verify UI state is through manual end-to-end testing in Chrome. By executing user-provided test scenarios, you can identify navigation problems, UI errors, and broken interactive elements just like a human QA engineer.

Do I need any special dependencies or frameworks to start manual end-to-end testing?▼

You do not need any special dependencies or frameworks to start manual end-to-end testing. The skill operates independently without external requirements, allowing you to simply open your test page in Chrome and follow the provided test scenario.

How do I execute test scenarios to confirm feature functionality before release?▼

To execute test scenarios and confirm feature functionality, start the browser test to open your target page in Chrome. You then manually perform the specified actions and verify the application behaviors to ensure new features work correctly before public release.

Why does manual feature verification require a user to interact with the browser?▼

Manual feature verification requires user interaction because the process simulates a QA engineer-like approach to validation. It actively depends on human input to navigate web pages, trigger form interactions, and confirm visual state rather than running automated scripts.