QA Test Scenario Generator

Test scenarios

by phuryn · MIT license · ★ 26,557 on GitHub · updated Sep 14

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or…

---
name: test-scenarios
description: "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation."
---
# Test Scenarios

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.

**Use when:** Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.

**Arguments:**
- `$PRODUCT`: The product or system name
- `$USER_STORY`: The user story to test (title and acceptance criteria)
- `$CONTEXT`: Additional testing context or constraints

## Step-by-Step Process

1. **Review the user story** and acceptance criteria

Overview

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.

What you get

Comprehensive test scenarios for each acceptance criterion
Clear test objectives aligned with user story intent
Detailed step-by-step test actions
Observable expected outcomes after each step
Edge case and error scenario coverage
Ready for QA team execution and documentation

Manual install (npx, ZIP)

Claude Codenpx skills add phuryn/pm-skills --skill test-scenarios -g -a claude-code

Claude Code (degit)npx degit phuryn/pm-skills/pm-execution/skills/test-scenarios#main ~/.claude/skills/test-scenarios

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.4 KB

Read SKILL.md here

phuryn/main1 file shown

SKILL.md3.4 KB

Browse every file on GitHub↗

SKILL.md

Show the full text87 lines

test-scenarios/SKILL.md87 lines · 3.4 KB

PreviewCode

Outline

RawView on GitHub

Test Scenarios

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.

Use when: Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.

Arguments:

$PRODUCT: The product or system name
$USER_STORY: The user story to test (title and acceptance criteria)
$CONTEXT: Additional testing context or constraints

Step-by-Step Process

Review the user story and acceptance criteria
Define test objectives - What specific behavior to validate
Establish starting conditions - System state, data setup, configurations
Identify user roles - Who performs the test actions
Create test steps - Break down interactions step-by-step
Define expected outcomes - Observable results after each step
Consider edge cases - Invalid inputs, boundary conditions
Output detailed test scenarios - Ready for QA execution

Scenario Template

Test Scenario: [Clear scenario name]

Test Objective: [What this test validates]

Starting Conditions:

[System state required]
[Data or configuration needed]
[User setup or permissions]

User Role: [Who performs the test]

Test Steps:

[First action and its expected result]
[Second action and observable outcome]
[Third action and system behavior]
[Completion action and final state]

Expected Outcomes:

[Observable result 1]
[Observable result 2]
[Observable result 3]

Example Test Scenario

Test Scenario: View Recently Viewed Products on Product Page

Test Objective: Verify that the 'Recently viewed' section displays correctly and excludes the current product.

Starting Conditions:

User is logged in or has browser history enabled
User has viewed at least 2 products in the current session
User is now on a product page different from previously viewed items

User Role: Online Shopper

Test Steps:

Navigate to any product page → Section should appear at bottom with previously viewed items
Scroll to bottom of page → "Recently viewed" section is visible with product cards
Verify product thumbnails → Images, titles, and prices are displayed correctly
Check current product → Current product is NOT in the recently viewed list
Click on a product card → User navigates to the corresponding product page

Expected Outcomes:

Recently viewed section appears only after viewing at least 1 prior product
Section displays 4-8 product cards with complete information
Current product is excluded from the list
Each card shows "Viewed X minutes/hours ago" timestamp
Clicking cards navigates to correct product pages
Performance: Section loads within 2 seconds

Output Deliverables

Comprehensive test scenarios for each acceptance criterion
Clear test objectives aligned with user story intent
Detailed step-by-step test actions
Observable expected outcomes after each step
Edge case and error scenario coverage
Ready for QA team execution and documentation

1	---
2	name: test-scenarios
3	description: "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation."
4	---
5	# Test Scenarios
6
7	Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.
8
9	Use when: Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.
10
11	Arguments:
12	- `$PRODUCT`: The product or system name
13	- `$USER_STORY`: The user story to test (title and acceptance criteria)
14	- `$CONTEXT`: Additional testing context or constraints
15
16	## Step-by-Step Process
17
18	1. Review the user story and acceptance criteria
19	2. Define test objectives - What specific behavior to validate
20	3. Establish starting conditions - System state, data setup, configurations
21	4. Identify user roles - Who performs the test actions
22	5. Create test steps - Break down interactions step-by-step
23	6. Define expected outcomes - Observable results after each step
24	7. Consider edge cases - Invalid inputs, boundary conditions
25	8. Output detailed test scenarios - Ready for QA execution
26
27	## Scenario Template
28
29	Test Scenario: [Clear scenario name]
30
31	Test Objective: [What this test validates]
32
33	Starting Conditions:
34	- [System state required]
35	- [Data or configuration needed]
36	- [User setup or permissions]
37
38	User Role: [Who performs the test]
39
40	Test Steps:
41	1. [First action and its expected result]
42	2. [Second action and observable outcome]
43	3. [Third action and system behavior]
44	4. [Completion action and final state]
45
46	Expected Outcomes:
47	- [Observable result 1]
48	- [Observable result 2]
49	- [Observable result 3]
50
51	## Example Test Scenario
52
53	Test Scenario: View Recently Viewed Products on Product Page
54
55	Test Objective: Verify that the 'Recently viewed' section displays correctly and excludes the current product.
56
57	Starting Conditions:
58	- User is logged in or has browser history enabled
59	- User has viewed at least 2 products in the current session
60	- User is now on a product page different from previously viewed items
61
62	User Role: Online Shopper
63
64	Test Steps:
65	1. Navigate to any product page → Section should appear at bottom with previously viewed items
66	2. Scroll to bottom of page → "Recently viewed" section is visible with product cards
67	3. Verify product thumbnails → Images, titles, and prices are displayed correctly
68	4. Check current product → Current product is NOT in the recently viewed list
69	5. Click on a product card → User navigates to the corresponding product page
70
71	Expected Outcomes:
72	- Recently viewed section appears only after viewing at least 1 prior product
73	- Section displays 4-8 product cards with complete information
74	- Current product is excluded from the list
75	- Each card shows "Viewed X minutes/hours ago" timestamp
76	- Clicking cards navigates to correct product pages
77	- Performance: Section loads within 2 seconds
78
79	## Output Deliverables
80
81	- Comprehensive test scenarios for each acceptance criterion
82	- Clear test objectives aligned with user story intent
83	- Detailed step-by-step test actions
84	- Observable expected outcomes after each step
85	- Edge case and error scenario coverage
86	- Ready for QA team execution and documentation
87