AgentAlley
Submit

Test scenarios skill

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

by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗

Use now

Files of Test scenarios

phuryn/main1 file shown
SKILL.md
Show the full text87 lines
test-scenarios/SKILL.md87 lines · 3.4 KB
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

  1. Review the user story and acceptance criteria
  2. Define test objectives - What specific behavior to validate
  3. Establish starting conditions - System state, data setup, configurations
  4. Identify user roles - Who performs the test actions
  5. Create test steps - Break down interactions step-by-step
  6. Define expected outcomes - Observable results after each step
  7. Consider edge cases - Invalid inputs, boundary conditions
  8. 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:

  1. [First action and its expected result]
  2. [Second action and observable outcome]
  3. [Third action and system behavior]
  4. [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:

  1. Navigate to any product page → Section should appear at bottom with previously viewed items
  2. Scroll to bottom of page → "Recently viewed" section is visible with product cards
  3. Verify product thumbnails → Images, titles, and prices are displayed correctly
  4. Check current product → Current product is NOT in the recently viewed list
  5. 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---
2name: test-scenarios
3description: "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 
7Create 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 
181. **Review the user story** and acceptance criteria
192. **Define test objectives** - What specific behavior to validate
203. **Establish starting conditions** - System state, data setup, configurations
214. **Identify user roles** - Who performs the test actions
225. **Create test steps** - Break down interactions step-by-step
236. **Define expected outcomes** - Observable results after each step
247. **Consider edge cases** - Invalid inputs, boundary conditions
258. **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:**
411. [First action and its expected result]
422. [Second action and observable outcome]
433. [Third action and system behavior]
444. [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:**
651. Navigate to any product page → Section should appear at bottom with previously viewed items
662. Scroll to bottom of page → "Recently viewed" section is visible with product cards
673. Verify product thumbnails → Images, titles, and prices are displayed correctly
684. Check current product → Current product is NOT in the recently viewed list
695. 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 

Discussion

Alternatives

Academy guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Business & ops · Apache-2.0Analyze feature requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions. · MITAdvocacy program designerUse when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规Business & ops · Apache-2.0Act as a product managerGuides the AI to act as a product manager, assisting in writing product requirement documents and addressing product-related queries.Business & ops · CC0-1.0

Browse more free Claude skills or everything in Product.