본문으로 건너뛰기
cccskills
무료GitHub에 공개

test-scenarios

Turn user stories and acceptance criteria into detailed test scenarios. Define objectives, starting conditions, user roles, actions, and observable results, including invalid inputs and boundary cases, so a quality assurance team can carry out the checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

  • Writing test cases from user stories
  • Preparing acceptance test scenarios
  • Checking invalid inputs and boundary cases
  • Documenting test procedures for a QA team

포함된 파일(1)

  • SKILL.md3.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

phuryn의 스킬 모두 보기

이 스킬의 문제 신고