qa-plan

Generate structured end-to-end test plans from scenario catalogs and feature requirements.

2|1|Updated May 27, 2025
One-click install
npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-plan-virtocommerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-plan
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-plan-virtocommerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA teams avoid reinventing test coverage by transforming feature requests, domains, and tickets into structured end-to-end test plans based on an existing scenario catalog.

Core Features & Use Cases

  • Scenario-Based Planning: Maps features and JIRA tickets to relevant business domains and reusable E2E scenarios.
  • Detailed Test Case Generation: Produces test cases with steps, expected results, priorities, edge cases, and regression traceability.
  • Use Case: A QA engineer can plan testing for a checkout change by identifying impacted domains, expanding matching scenarios, and preparing TestRail-compatible artifacts.

Quick Start

Use the qa-plan skill to create a complete test plan for the checkout feature including test cases and regression mappings.

Frequently Asked Questions about qa-plan

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

FAQPage Schema
How do I generate an E2E test plan from JIRA tickets and feature requirements?

You can generate an E2E test plan by mapping JIRA tickets and feature requests to relevant business domains and reusable scenarios. This process creates structured test cases with steps, expected results, priorities, and regression traceability.

How do I create TestRail-compatible test cases for regression suite planning?

Create TestRail-compatible test cases by expanding mapped E2E scenarios into detailed steps, expected results, and edge cases. The generated artifacts include priorities and regression mappings required for direct TestRail import.

What is scenario-based test planning for E2E testing?

Scenario-based test planning maps product features and JIRA tickets to existing business domains and reusable E2E scenarios. It avoids reinventing test coverage by transforming cataloged scenarios into structured end-to-end test plans.

Can I map JIRA tickets to business domains for E2E test coverage?

Yes, you can map JIRA tickets to business domains by aligning feature requirements with an existing scenario catalog. This identifies impacted domains and expands matching scenarios to ensure comprehensive E2E test coverage.

How do I ensure traceability tracking in E2E test cases?

Ensure traceability tracking by generating test cases that link steps, expected results, and edge cases back to original feature requirements and JIRA tickets. This provides regression suite planning with verifiable coverage mappings.

What's the best way to plan testing for a checkout feature change without reinventing coverage?

The best way to plan testing for a checkout change is to identify impacted business domains, expand matching cataloged E2E scenarios, and generate detailed test cases. This reuses existing coverage to produce traceable test plans.