skills.rest
youhei-ushio
youhei-ushioCOMMUNITY
Explore all skills by this author →
GitHub

affected-area-testing

Validate codebase changes with Playwright-based web testing scenarios.

1|Updated May 21, 2026
Search Tags:#software testing#regression testing#browser testing#test plan#feature validation
One-click install
npx skills add https://github.com/youhei-ushio/dotclaude-public --skill affected-area-testing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: affected-area-testing
Source: https://github.com/youhei-ushio/dotclaude-public/tree/main/skills/global/affected-area-testing
Command: npx skills add https://github.com/youhei-ushio/dotclaude-public --skill affected-area-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the functionality and integrity of code modifications through a systematic test plan, minimizing regressions and bugs in software releases.

Core Features & Use Cases

  • Pre-PR Testing: Assesses code changes for any issues before Pull Request creation.
  • 4-Step Verification: Conducts Basic, New Feature, Integration, and Regression Testing to ensure a consistent and stable system.
  • Browser-Based Execution: Utilizes Playwright MCP for actual browser operations for thorough testing.
  • Documentation & Standards: Emphasizes clear documentation of the test results with easy-to-follow indicators for success or failure.

Quick Start

To begin testing after code modifications, activate the skill with 'run affected-area-testing'.

Frequently Asked Questions about affected-area-testing

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

FAQPage Schema
How do I automate regression testing for modified features before creating a pull request?▼

Automate regression testing by activating the skill to execute a 4-step verification process covering basic, new feature, integration, and regression checks. This validates code modifications for consistency and stability before PR creation.

What is affected area testing and when do I need it for software releases?▼

Affected area testing is a post-modification assurance methodology that validates codebase changes to minimize regressions and bugs. You need it after modifying features to ensure system integrity and stability before software releases.

Can I use Playwright for browser-based feature validation and integration testing?▼

Yes, you can use Playwright for browser-based feature validation. The skill utilizes Playwright's web automation capabilities to execute actual browser operations, enabling thorough integration and regression testing in web environments.

How do I run a comprehensive test plan for code changes in a web environment?▼

Run a comprehensive test plan by activating the skill with 'run affected-area-testing'. It conducts basic, new feature, integration, and regression testing sequentially, documenting test results with clear success or failure indicators.

Does this testing methodology support both individual and suite-based test scenarios?▼

Yes, the testing methodology supports both individual and suite-based test scenarios. It validates and verifies codebase modifications using Playwright's web automation, ensuring consistent and stable system behavior across different testing scopes.

Related Skills

Explore More Software Engineering Skills→
botPhUbotPhU

playwright-expert

Automate end-to-end browser testing with Playwright across Chromium, Firefox, and WebKit.

Community
Intermediate
stacklokstacklok
4

upstream-release-docs

Analyze upstream releases and update documentation with source-verified change tracking.

Official
Advanced
gajjalaashok75-UIgajjalaashok75-UI
2

e2e-testing

Builds Playwright-based end-to-end browser test suites for CI/CD pipelines.

Community
Advanced
betaTridentbetaTrident

browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Community
Advanced