Test Scenarios

What Is This?

Overview

Test Scenarios is a structured skill for generating comprehensive test cases directly from user stories. It transforms high-level feature descriptions into actionable, detailed test documentation that includes test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Rather than writing test cases from scratch, teams can use this skill to produce consistent, thorough test scenarios in a fraction of the time.

The skill follows a standardized format that aligns with common QA practices and acceptance testing frameworks. Each generated scenario captures not just what to test, but who performs the test, under what conditions, and what a passing result looks like. This removes ambiguity from the testing process and ensures that developers, testers, and product managers share a common understanding of what constitutes a working feature.

By grounding test scenarios in user stories, this skill keeps testing focused on real user behavior rather than technical implementation details. The output is practical documentation that can feed directly into test management tools, sprint planning sessions, or formal QA processes.

Who Should Use This

• QA engineers who need to produce structured test cases quickly from product requirements
• Product managers who want to define acceptance criteria before development begins
• Developers who practice test-driven development and need clear behavioral specifications
• Scrum masters and agile coaches who facilitate definition-of-done conversations
• Business analysts who translate stakeholder requirements into verifiable test conditions
• Technical writers who document feature behavior for internal or external audiences

Why Use It?

Problems It Solves

• Inconsistent test documentation across team members leads to missed edge cases and duplicated effort
• User stories often lack explicit acceptance criteria, leaving testers to guess what a passing state looks like
• Manual test case writing is time-consuming and prone to gaps when done under sprint pressure
• Handoffs between product and QA teams frequently lose context about intended user behavior
• Test plans written without a standard structure are difficult to review, maintain, or reuse

Core Highlights

• Generates test scenarios directly from user story input
• Produces structured output with objectives, preconditions, roles, steps, and expected results
• Supports happy path, edge case, and negative test scenario generation
• Maintains consistent formatting suitable for test management tools
• Reduces the time from story writing to test-ready documentation
• Aligns QA output with product intent by anchoring tests to user behavior
• Scales across feature types including UI flows, API interactions, and business logic

How to Use It?

Basic Usage

Provide a user story as input and the skill returns a fully structured test scenario. A typical input looks like this:

User Story:
As a registered user, I want to reset my password via email
so that I can regain access to my account if I forget my credentials.

The skill produces output in this format:

Test Scenario: Password Reset via Email

Objective: Verify that a registered user can successfully reset their password
           using the email-based reset flow.

Starting Conditions:
- User has a registered account with a verified email address
- User is logged out of the application
- Email service is operational

User Role: Registered user (unauthenticated)

Steps:
1. Navigate to the login page
2. Click "Forgot Password"
3. Enter the registered email address
4. Submit the form
5. Open the reset email and click the reset link
6. Enter and confirm a new password
7. Submit the new password form

Expected Outcome:
- User receives a reset email within 2 minutes
- Reset link is valid for the configured expiry period
- User can log in with the new password
- Old password no longer grants access

Specific Scenarios

For negative testing, specify that the input should include invalid or boundary conditions, such as an unregistered email address or an expired reset token. For API-level testing, the user story can describe an endpoint interaction, and the skill will generate request-level steps with expected HTTP responses.

Real-World Examples

A product team writing stories for a checkout flow can generate test scenarios covering successful payment, declined card handling, and session timeout during checkout. A mobile development team can use the skill to produce scenarios for offline behavior and network interruption during data sync.

Important Notes

Requirements

• Input must include a clear user story with a defined goal and user role
• The feature being tested should have enough detail to identify at least one success condition
• Access to the skill requires a configured environment with the pm-skills source enabled