‹ 首页

test-scenarios

@phuryn · 收录于 1 周前 · 上游提交 1 周前★ 社区精选

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.

适合你,如果需要从用户故事快速生成结构化的测试场景

/ 通过 npx 安装 校验哈希
npx oh-my-skill add phuryn/pm-skills/test-scenarios
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- phuryn/pm-skills/test-scenarios
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify phuryn/pm-skills/test-scenarios
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
23265GitHub stars
~709上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 18468a9 · 表述以原文为准
它做什么

安装后,Claude 能根据用户故事生成完整的测试场景,包括测试目标、起始条件、用户角色、逐步操作步骤和预期结果。

什么时候触发

当你需要编写 QA 测试用例、创建测试计划、定义验收测试或验证功能实现时触发。

装好后可以这样说
Claude 会输出包含测试步骤和预期结果的详细场景。
Claude 会分析故事并生成对应的测试场景。
技能原文 SKILL.md作者撰写 · MIT · 18468a9

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
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。