test-scenario.template.yaml 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192
  1. # WDS Test Scenario Template
  2. # Save to: test-scenarios/TS-XXX-name.yaml
  3. test_scenario:
  4. id: "TS-XXX" # Format: TS-001, TS-002, etc.
  5. name: "Feature Testing" # Human-readable name
  6. delivery_id: "DD-XXX" # Related Design Delivery
  7. type: "user_acceptance" # user_acceptance | integration | e2e
  8. status: "ready" # ready | in_progress | blocked
  9. tester: "designer" # designer | qa | developer
  10. created_at: "YYYY-MM-DDTHH:MM:SSZ"
  11. test_objectives:
  12. - "Validate implementation matches design specifications"
  13. - "Verify user flow is intuitive and smooth"
  14. - "Confirm all edge cases are handled"
  15. - "Ensure design system components are used correctly"
  16. - "Test accessibility and usability"
  17. test_environment:
  18. devices:
  19. - "Device 1 (OS version)"
  20. - "Device 2 (OS version)"
  21. test_data:
  22. - field: "value"
  23. - field: "value"
  24. # Happy Path Tests
  25. happy_path:
  26. - id: "HP-001"
  27. name: "Main User Flow"
  28. priority: "critical" # critical | high | medium | low
  29. steps:
  30. - action: "[User action]"
  31. expected: "[Expected result]"
  32. design_ref: "[Path to specification]#[section]"
  33. - action: "[User action]"
  34. expected: "[Expected result]"
  35. design_ref: "[Path to specification]#[section]"
  36. success_criteria:
  37. - "[Success criterion 1]"
  38. - "[Success criterion 2]"
  39. - "[Success criterion 3]"
  40. # Error State Tests
  41. error_states:
  42. - id: "ES-001"
  43. name: "Error Scenario"
  44. priority: "high"
  45. steps:
  46. - action: "[Action that triggers error]"
  47. - expected: "[Expected error message]"
  48. - expected: "[Expected recovery option]"
  49. - design_ref: "[Path to specification]#[error-section]"
  50. success_criteria:
  51. - "[Error handling criterion 1]"
  52. - "[Error handling criterion 2]"
  53. # Edge Case Tests
  54. edge_cases:
  55. - id: "EC-001"
  56. name: "Edge Case Scenario"
  57. priority: "medium"
  58. steps:
  59. - action: "[Unusual action]"
  60. - expected: "[Expected handling]"
  61. - design_ref: "[Path to specification]#[edge-case-section]"
  62. success_criteria:
  63. - "[Edge case criterion 1]"
  64. # Design System Validation
  65. design_system_checks:
  66. - id: "DS-001"
  67. name: "Component Validation"
  68. checks:
  69. - component: "Component Name"
  70. instances: ["Location 1", "Location 2"]
  71. verify:
  72. - "[Visual property 1]"
  73. - "[Visual property 2]"
  74. - "[State behavior 1]"
  75. design_ref: "D-Design-System/path/to/component.md"
  76. # Accessibility Tests
  77. accessibility:
  78. - id: "A11Y-001"
  79. name: "Screen Reader Navigation"
  80. priority: "high"
  81. setup: "Enable screen reader (VoiceOver/TalkBack)"
  82. steps:
  83. - action: "[Navigate with screen reader]"
  84. - verify:
  85. - "[Accessibility check 1]"
  86. - "[Accessibility check 2]"
  87. success_criteria:
  88. - "[Accessibility criterion 1]"
  89. - "[Accessibility criterion 2]"
  90. # Usability Tests
  91. usability:
  92. - id: "UX-001"
  93. name: "First Impression"
  94. type: "observational"
  95. instructions: |
  96. [Instructions for conducting usability test]
  97. success_criteria:
  98. - "[Usability criterion 1]"
  99. - "[Usability criterion 2]"
  100. # Performance Tests
  101. performance:
  102. - id: "PERF-001"
  103. name: "Performance Check"
  104. verify:
  105. - "[Performance metric 1]"
  106. - "[Performance metric 2]"
  107. success_criteria:
  108. - "[Performance target 1]"
  109. - "[Performance target 2]"
  110. # Test Report Template
  111. report_template:
  112. sections:
  113. - name: "Test Summary"
  114. fields:
  115. - "Date tested"
  116. - "Tester name"
  117. - "Device tested"
  118. - "Build version"
  119. - "Overall result (Pass/Fail/Partial)"
  120. - name: "Happy Path Results"
  121. fields:
  122. - "Test ID"
  123. - "Result (Pass/Fail)"
  124. - "Notes"
  125. - "Screenshots"
  126. - name: "Issues Found"
  127. fields:
  128. - "Issue ID"
  129. - "Severity (Critical/High/Medium/Low)"
  130. - "Description"
  131. - "Steps to reproduce"
  132. - "Expected vs Actual"
  133. - "Screenshot/Video"
  134. - "Design reference violated"
  135. - name: "Design System Compliance"
  136. fields:
  137. - "Component"
  138. - "Compliant (Yes/No)"
  139. - "Deviations noted"
  140. - name: "Recommendations"
  141. fields:
  142. - "What worked well"
  143. - "What needs improvement"
  144. - "Suggested changes"
  145. # Sign-off Criteria
  146. sign_off:
  147. required_for_approval:
  148. - "All critical tests pass"
  149. - "No critical or high severity issues"
  150. - "Design system compliance > 95%"
  151. - "Accessibility tests pass"
  152. - "Usability metrics meet targets"
  153. designer_approval:
  154. statement: |
  155. I confirm that the implemented feature matches the design
  156. specifications and meets the quality standards defined in
  157. this test scenario.
  158. signature: "________________"
  159. date: "________________"