qa-testing

Detect test stacks and generate test plans with framework recommendations.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gfcampos1/my-skills --skill qa-testing-gfcampos1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-testing
Source: https://github.com/gfcampos1/my-skills/tree/main/skills/qa-testing
Command: npx skills add https://github.com/gfcampos1/my-skills --skill qa-testing-gfcampos1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides structured guidance to ensure tests are appropriate, complete, and maintainable so teams avoid brittle suites, missed edge cases, and poor coverage decisions.

Core Features & Use Cases

  • Test stack detection: Inspect project configs and dependencies to detect existing frameworks and follow established conventions.
  • Strategy & framework selection: Recommend unit, integration, component, and E2E frameworks and setup snippets tailored to Node/TypeScript, Python, and frontend stacks.
  • Test planning and quality: Produce actionable test plans with happy paths, edge cases, security checks, and coverage targets, plus rules for writing tests (AAA, isolation, mocks).
  • Use Case: On a new React + Vite project, recommend Vitest + RTL for components, MSW for integration, and Playwright for critical E2E flows, then produce a test plan for a login flow.

Quick Start

Ask the skill to "Create a test plan and framework recommendation for the POST /transactions route, prioritizing unit and integration tests."

Frequently Asked Questions about qa-testing

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

FAQPage Schema
How do I create a test plan for automated API and E2E testing?

To create an automated test plan, define happy paths, edge cases, and security checks for your API and E2E flows. This process generates a structured plan enforcing AAA patterns, isolated mocks, and coverage targets to ensure your tests are maintainable and complete.

What testing frameworks should I use for a React and TypeScript project?

For React and TypeScript testing, select frameworks like Vitest and RTL for components, MSW for integration, and Playwright for critical E2E flows. Recommendations are tailored to your existing stack to follow established project conventions and CI setups.

How do I detect existing test frameworks and CI setups in my project?

Detecting existing test frameworks involves inspecting your project configs and dependencies to identify established conventions. This stack detection ensures new test plans and framework recommendations integrate seamlessly with your current JavaScript, Python, or frontend environments.

What are the best practices for writing reliable unit and integration tests?

Best practices for reliable unit and integration tests include following the AAA pattern, maintaining test isolation, and using isolated mocks. Enforcing these test-quality rules prevents brittle suites and ensures your coverage targets accurately reflect application health.

Does this approach work for both Python and JavaScript test automation?

Yes, this test planning approach works across JavaScript, TypeScript, and Python projects. It detects your existing test stack and recommends compatible unit, integration, component, and E2E frameworks tailored to your specific language and web frontend environment.

Why are my automated tests brittle and how do I fix them?

Automated tests become brittle due to missed edge cases, poor isolation, and lack of structured coverage targets. Fix brittle suites by generating actionable test plans that enforce best practices like AAA patterns and isolated mocks for unit and integration testing.