AI Skill Report Card

Generating Test Cases

A-85·May 9, 2026·Source: Web
15 / 15
Input PRD content → Analyze requirements → Generate test cases with:
- Numbered steps (at least 1)
- Verifiable expected results (at least 1)
- Priority: P1(20%) + P2(30%) + P3(30%) + P4(20%)
- Coverage: Functional, Performance, Security, Compatibility
Recommendation
Add specific templates or frameworks section with reusable test case formats
14 / 15

Progress:

  • Parse PRD content (text + images)
  • Identify core features and edge cases
  • Design test scenarios by type
  • Assign priorities based on business impact
  • Format with numbered steps and clear expectations

Step 1: Requirement Analysis

  • Extract functional requirements from text
  • Analyze UI mockups/wireframes for interaction flows
  • Identify data inputs, outputs, and business rules

Step 2: Test Type Classification

  • Functional: Core feature behavior, user workflows
  • Performance: Response times, load handling, resource usage
  • Security: Authentication, authorization, data protection
  • Compatibility: Browser/device/OS coverage

Step 3: Priority Assignment

  • P1 (20%): Critical path, blocking issues
  • P2 (30%): Important features, common scenarios
  • P3 (30%): Standard functionality, edge cases
  • P4 (20%): Nice-to-have, rare scenarios
Recommendation
Include edge case identification techniques beyond basic functional/non-functional categories
20 / 20

Example 1: Input: Login feature PRD with username/password fields Output:

TC001 [P1-Functional] Valid Login
Steps:
1. Navigate to login page
2. Enter valid username "user@test.com"
3. Enter valid password "Pass123!"
4. Click login button
Expected: User redirected to dashboard, session established

TC002 [P2-Security] Password Masking
Steps:
1. Navigate to login page  
2. Click password field
3. Type "password123"
Expected: Password characters displayed as dots/asterisks

Example 2: Input: Mobile app checkout flow with payment integration Output:

TC015 [P1-Functional] Complete Purchase Flow
Steps:
1. Add item to cart
2. Navigate to checkout
3. Enter shipping details
4. Select payment method "Credit Card"
5. Enter card details: 4111111111111111, 12/25, 123
6. Tap "Place Order"
Expected: Order confirmation displayed, payment processed, email sent

TC016 [P2-Performance] Checkout Load Time
Steps:
1. Start timer
2. Navigate to checkout page with 5 items in cart
3. Stop timer when page fully loads
Expected: Page loads within 3 seconds on 3G connection
Recommendation
Provide default test data sets or generation patterns for common scenarios
  • Clear Steps: Use action verbs, specify exact inputs
  • Measurable Results: Include specific values, states, messages
  • Realistic Data: Use valid test data formats
  • Environment Context: Specify browser, device, network conditions when relevant
  • Traceability: Link test cases to specific requirements
  • Maintainable: Write steps that remain valid across minor UI changes
  • Vague expected results ("system works correctly")
  • Missing negative test cases
  • Unrealistic priority distribution (too many P1s)
  • Ignoring non-functional requirements
  • Steps too high-level or too granular
  • Not considering real user behavior patterns
  • Forgetting error handling scenarios
  • Missing cross-browser/device coverage for web apps
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
15/15
Workflow
14/15
Examples
20/20
Completeness
18/20
Format
15/15
Conciseness
13/15