webapp-testing

Automate UI testing for web applications using Browser MCP and Storybook.

341|48|Updated Apr 4, 2025
One-click install
npx skills add https://github.com/WellApp-ai/Well --skill webapp-testing-wellapp-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webapp-testing
Source: https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/webapp-testing
Command: npx skills add https://github.com/WellApp-ai/Well --skill webapp-testing-wellapp-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated testing of web applications' user interfaces using Browser MCP and Storybook, reducing manual QA effort and speeding up release cycles.

Core Features & Use Cases

  • UI Component Testing: Validate Storybook components render correctly and interact as expected.
  • Integration Testing: Verify end-to-end user flows on the dev server.
  • Troubleshooting: Capture and review browser console messages and network requests to diagnose failures.

Quick Start

Start Storybook with npm run storybook, then open http://localhost:6006 and perform snapshots with browser_snapshot. Start the dev server with npm run dev, open http://localhost:3000, and use browser_click, browser_type, and browser_snapshot to validate interactions.

Frequently Asked Questions about webapp-testing

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

FAQPage Schema
How do I automate UI testing for Storybook components?

Automate UI testing for Storybook components by starting the Storybook server, navigating to localhost:6006 with browser_navigate, and using browser_snapshot to validate rendering and interactions. This replaces manual QA and speeds up release cycles for web applications.

Can I run end-to-end web app testing on a local development server?

Yes, you can run end-to-end web app testing on a local dev server. Start the server with npm run dev, open localhost:3000, and use browser_click, browser_type, and browser_snapshot to verify full user flows and interactions.

What is Browser MCP used for in web app testing?

Browser MCP is used in web app testing to automate browser interactions like navigating, clicking, typing, and capturing snapshots. It enables both component testing in Storybook and integration testing on dev servers to reduce manual verification effort.

How do I troubleshoot UI test failures and capture browser console messages?

Troubleshoot UI test failures by capturing and reviewing browser console messages and network requests during automated testing. Using Browser MCP commands like browser_snapshot helps diagnose rendering issues and interaction failures on Storybook or dev server pages.

Do I need Storybook and a dev server running to perform component and integration testing?

Yes, you need Storybook and a dev server running to perform component and integration testing. The Skill requires npm run storybook for component validation and npm run dev for end-to-end UI verification on local development environments.