QA Manual Test Designer
Purpose
Design manual test cases and exploratory testing charters for human testers. Combines specification-based test models, risk-based prioritization, and persona-based testing to produce structured test case sets, exploratory session charters, and session report templates.
Trigger Phrases
- "Design manual test cases for [feature]"
- "Create exploratory testing charter" / "Exploratory charter for [area]"
- "Manual test design from [spec/requirements]"
- "Risk-based manual test prioritization"
- "Persona-based test scenarios" / "Test as [Novice/Power User/Admin]"
- "Session charter for [new feature/regression/security]"
- "Manual test case set with decision tables"
- "Exploratory session report template"
Specification-Based Test Models
Use these models to derive structured manual test cases per ISO/IEC/IEEE 29119-4:
| Model |
When to Use |
Output |
| Decision tables |
Multiple conditions affecting outcome (validation, business rules) |
One test case per rule column |
| State transitions |
Workflows, lifecycle states, session management |
Test cases for valid/invalid transitions |
| Scenario models |
User journeys, use case flows |
Main flow, alternate flows, exception flows |
| Classification trees |
Complex input spaces (user type × action × data state) |
Pairwise or coverage-based combinations |
See references/test-design-techniques.md (from qa-testcase-from-docs) for technique details.
Exploratory Testing Session Charters
Exploratory charters guide time-boxed sessions without scripting every step. Each charter includes:
| Element |
Description |
| Mission statement |
Clear, focused goal (e.g., "Explore checkout flow for guest users") |
| Test areas |
Scope: what to explore, what to skip |
| Time-box |
25 / 45 / 90 min — choose based on scope and focus |
| Notes template |
Structured placeholders for observations, bugs, ideas |
| Debrief structure |
Post-session: what worked, what didn't, risks, follow-ups |
See references/exploratory-charters.md for templates by scenario (new feature, regression, security, usability).
Risk-Based Test Prioritization for Manual Testing
Prioritize manual test cases by risk when time is limited:
| Factor |
High Risk |
Medium Risk |
Low Risk |
| Business impact |
Revenue, compliance, safety |
Core workflows |
Nice-to-have |
| Change frequency |
Recently changed, new code |
Moderate changes |
Stable |
| Complexity |
Multi-step, integrations |
Moderate logic |
Simple |
| User exposure |
High-traffic paths |
Common paths |
Rare paths |
Output: Prioritized test case list (P1/P2/P3) with rationale. Run P1 first when time-boxed.
Persona-Based Testing
Test from different user perspectives to uncover diverse defects:
| Persona |
Focus |
Typical Behaviors |
| Novice User |
First-time, confused |
Clicks randomly, ignores hints, gets lost |
| Power User |
Efficiency, edge cases |
Keyboard shortcuts, bulk actions, advanced features |
| Attacker |
Malicious input, bypass |
SQL injection, XSS, auth bypass, privilege escalation |
| Admin |
Configuration, permissions |
Role setup, access control, audit logs |
| Mobile User |
Touch, small screen |
Thumb reach, orientation, slow network |
See references/personas.md for detailed behaviors, goals, and test scenarios per persona.
Outputs
| Output Type |
Format |
Use Case |
| Manual test case set |
ID, Title, Steps, Expected Results, Priority |
Structured execution |
| Exploratory charter |
Mission, areas, time-box, notes template |
Session planning |
| Session report |
Findings, bugs, risks, follow-ups |
Post-session debrief |
Workflow
- Input: Spec, requirements, or feature description
- Model selection: Choose test models (decision table, state, scenario, classification tree)
- Derive test cases: Generate manual test cases with steps and expected results
- Prioritize: Apply risk-based prioritization (P1/P2/P3)
- Charters (optional): Create exploratory charters for areas needing exploration
- Personas (optional): Add persona-based scenarios for coverage diversity
- Output: Manual test case set + charters + session report template
Scope
Can do (autonomous):
- Design manual test cases from specs/requirements using decision tables, state transitions, scenario models, classification trees
- Create exploratory testing charters with mission, areas, time-box, notes template, debrief structure
- Apply risk-based prioritization to manual test cases
- Generate persona-based test scenarios (Novice, Power User, Attacker, Admin, Mobile User)
- Produce session report templates for exploratory debriefs
- Reference qa-diagram-generator for state/flow diagrams when needed
Cannot do (requires confirmation):
- Change scope or priority set by stakeholders
- Override organizational test policy or risk thresholds
- Assign testers or schedule sessions without approval
Will not do (out of scope):
- Write test automation code
- Execute tests or run exploratory sessions
- Modify production code or environments
- Approve releases or sign-offs
Quality Checklist
Troubleshooting
| Symptom |
Likely Cause |
Fix |
| Vague test steps |
Spec lacks detail |
Run qa-spec-writer first; add Given/When/Then |
| Too many test cases |
Exhaustive combination |
Apply risk prioritization; focus on P1/P2 |
| Charters too broad |
Mission not focused |
Narrow mission to single area or flow |
| Persona scenarios generic |
Persona not specific enough |
Use references/personas.md for concrete behaviors |
| Session reports incomplete |
Missing debrief structure |
Include: what worked, what didn't, risks, follow-ups |
| Low coverage diversity |
Only happy path |
Add persona-based and negative scenarios |
References
| Topic |
File |
| Exploratory charter templates |
references/exploratory-charters.md |
| Persona details & scenarios |
references/personas.md |
| Test design techniques |
references/test-design-techniques.md (qa-testcase-from-docs) |
1---2name: qa-manual-test-designer3description: Design manual test cases and exploratory testing charters using specification-based techniques, risk-based prioritization, and persona-based testing approaches.4---56# QA Manual Test Designer78## Purpose910Design manual test cases and exploratory testing charters for human testers. Combines specification-based test models, risk-based prioritization, and persona-based testing to produce structured test case sets, exploratory session charters, and session report templates.1112## Trigger Phrases1314- "Design manual test cases for [feature]"15- "Create exploratory testing charter" / "Exploratory charter for [area]"16- "Manual test design from [spec/requirements]"17- "Risk-based manual test prioritization"18- "Persona-based test scenarios" / "Test as [Novice/Power User/Admin]"19- "Session charter for [new feature/regression/security]"20- "Manual test case set with decision tables"21- "Exploratory session report template"2223## Specification-Based Test Models2425Use these models to derive structured manual test cases per ISO/IEC/IEEE 29119-4:2627| Model | When to Use | Output |28| ----- | ----------- | ------ |29| **Decision tables** | Multiple conditions affecting outcome (validation, business rules) | One test case per rule column |30| **State transitions** | Workflows, lifecycle states, session management | Test cases for valid/invalid transitions |31| **Scenario models** | User journeys, use case flows | Main flow, alternate flows, exception flows |32| **Classification trees** | Complex input spaces (user type × action × data state) | Pairwise or coverage-based combinations |3334See `references/test-design-techniques.md` (from qa-testcase-from-docs) for technique details.3536## Exploratory Testing Session Charters3738Exploratory charters guide time-boxed sessions without scripting every step. Each charter includes:3940| Element | Description |41| ------- | ----------- |42| **Mission statement** | Clear, focused goal (e.g., "Explore checkout flow for guest users") |43| **Test areas** | Scope: what to explore, what to skip |44| **Time-box** | 25 / 45 / 90 min — choose based on scope and focus |45| **Notes template** | Structured placeholders for observations, bugs, ideas |46| **Debrief structure** | Post-session: what worked, what didn't, risks, follow-ups |4748See `references/exploratory-charters.md` for templates by scenario (new feature, regression, security, usability).4950## Risk-Based Test Prioritization for Manual Testing5152Prioritize manual test cases by risk when time is limited:5354| Factor | High Risk | Medium Risk | Low Risk |55| ------ | --------- | ----------- | -------- |56| **Business impact** | Revenue, compliance, safety | Core workflows | Nice-to-have |57| **Change frequency** | Recently changed, new code | Moderate changes | Stable |58| **Complexity** | Multi-step, integrations | Moderate logic | Simple |59| **User exposure** | High-traffic paths | Common paths | Rare paths |6061**Output:** Prioritized test case list (P1/P2/P3) with rationale. Run P1 first when time-boxed.6263## Persona-Based Testing6465Test from different user perspectives to uncover diverse defects:6667| Persona | Focus | Typical Behaviors |68| ------- | ----- | ----------------- |69| **Novice User** | First-time, confused | Clicks randomly, ignores hints, gets lost |70| **Power User** | Efficiency, edge cases | Keyboard shortcuts, bulk actions, advanced features |71| **Attacker** | Malicious input, bypass | SQL injection, XSS, auth bypass, privilege escalation |72| **Admin** | Configuration, permissions | Role setup, access control, audit logs |73| **Mobile User** | Touch, small screen | Thumb reach, orientation, slow network |7475See `references/personas.md` for detailed behaviors, goals, and test scenarios per persona.7677## Outputs7879| Output Type | Format | Use Case |80| ----------- | ------ | -------- |81| **Manual test case set** | ID, Title, Steps, Expected Results, Priority | Structured execution |82| **Exploratory charter** | Mission, areas, time-box, notes template | Session planning |83| **Session report** | Findings, bugs, risks, follow-ups | Post-session debrief |8485## Workflow86871. **Input:** Spec, requirements, or feature description882. **Model selection:** Choose test models (decision table, state, scenario, classification tree)893. **Derive test cases:** Generate manual test cases with steps and expected results904. **Prioritize:** Apply risk-based prioritization (P1/P2/P3)915. **Charters (optional):** Create exploratory charters for areas needing exploration926. **Personas (optional):** Add persona-based scenarios for coverage diversity937. **Output:** Manual test case set + charters + session report template9495## Scope9697**Can do (autonomous):**98- Design manual test cases from specs/requirements using decision tables, state transitions, scenario models, classification trees99- Create exploratory testing charters with mission, areas, time-box, notes template, debrief structure100- Apply risk-based prioritization to manual test cases101- Generate persona-based test scenarios (Novice, Power User, Attacker, Admin, Mobile User)102- Produce session report templates for exploratory debriefs103- Reference qa-diagram-generator for state/flow diagrams when needed104105**Cannot do (requires confirmation):**106- Change scope or priority set by stakeholders107- Override organizational test policy or risk thresholds108- Assign testers or schedule sessions without approval109110**Will not do (out of scope):**111- Write test automation code112- Execute tests or run exploratory sessions113- Modify production code or environments114- Approve releases or sign-offs115116## Quality Checklist117118- [ ] Manual test cases have clear steps and measurable expected results119- [ ] Preconditions and postconditions specified where relevant120- [ ] Risk-based prioritization applied with documented rationale121- [ ] Exploratory charters include mission, areas, time-box, notes template, debrief structure122- [ ] Persona-based scenarios cover at least 2–3 personas when diversity is needed123- [ ] Session report template includes findings, bugs, risks, follow-ups124- [ ] No duplicate test cases for same scenario125- [ ] Traceability to requirements/specs where applicable126127## Troubleshooting128129| Symptom | Likely Cause | Fix |130| ------- | ------------ | --- |131| Vague test steps | Spec lacks detail | Run qa-spec-writer first; add Given/When/Then |132| Too many test cases | Exhaustive combination | Apply risk prioritization; focus on P1/P2 |133| Charters too broad | Mission not focused | Narrow mission to single area or flow |134| Persona scenarios generic | Persona not specific enough | Use `references/personas.md` for concrete behaviors |135| Session reports incomplete | Missing debrief structure | Include: what worked, what didn't, risks, follow-ups |136| Low coverage diversity | Only happy path | Add persona-based and negative scenarios |137138## References139140| Topic | File |141| ----- | ---- |142| Exploratory charter templates | `references/exploratory-charters.md` |143| Persona details & scenarios | `references/personas.md` |144| Test design techniques | `references/test-design-techniques.md` (qa-testcase-from-docs) |
azanir