web-app-testing

Test web applications manually across viewports and network conditions.

25|3|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill web-app-testing-nimadorostkar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-app-testing
Source: https://github.com/nimadorostkar/Claude-Skills-collection/tree/main/skills/testing/web-app-testing
Command: npx skills add https://github.com/nimadorostkar/Claude-Skills-collection --skill web-app-testing-nimadorostkar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of superficial manual testing by providing a rigorous, systematic framework for exploring web applications, ensuring that edge cases, network failures, and UI inconsistencies are identified before deployment.

Core Features & Use Cases

  • Systematic Exploration: Provides a structured checklist for happy paths, boundary conditions, and error states.
  • Technical Inspection: Guides the user through console and network tab analysis to catch silent failures.
  • Use Case: Use this when you need to verify a new feature or reproduce a complex bug, ensuring you check mobile viewports, network throttling, and state persistence.

Quick Start

Activate the web-app-testing skill to perform a comprehensive manual audit of the current feature flow and generate a detailed defect report.

Frequently Asked Questions about web-app-testing

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

FAQPage Schema
How do I systematically perform manual testing for a web application?

Systematic manual testing requires a structured checklist covering happy paths, boundary conditions, and error states. This skill provides that rigorous framework, guiding interactive browser exploration to verify features and identify UI inconsistencies before deployment.

How do I reproduce a complex bug using browser developer tools?

To reproduce a complex bug, you need to monitor console errors, network requests, and UI state transitions. This skill guides you through technical inspection of browser developer tools to catch silent failures and accurately replicate edge-case defects.

What is the best way to discover edge cases in web development QA?

Discovering edge cases in QA involves testing across various viewports and network conditions. This skill targets edge-case discovery by guiding you through network throttling, mobile viewport simulation, and state persistence verification.

Do I need active browser developer tools to inspect network requests during QA?

Yes, active browser developer tools are required. This skill requires you to monitor console errors and analyze network requests directly within the browser to catch silent failures and verify UI state transitions during feature exploration.

Can I use this systematic QA approach to verify state persistence across mobile viewports?

Yes, you can verify state persistence across mobile viewports. This skill explicitly targets feature verification across various viewports and network conditions, ensuring your web application maintains correct UI state transitions during mobile manual testing.