Exploratory testing charter template

Scripted tests check what you expect. Exploratory testing looks for what you did not expect. To keep it from turning into aimless tapping, give each session a charter: a short mission, a time box and a place to write notes. No QA background needed.

How a session works

1. Pick one mission (a sentence, not a list).
2. Set a timer for 30 minutes. Test only that mission.
3. Take notes as you go: what you tried, what surprised you.
4. At the end, write findings and questions, then decide the next charter.

Template (copy and paste)

CHARTER
Mission:  Explore <area / feature>
          with <resource: data, device, condition, persona>
          to discover <risk or kind of problem>

Build / device / OS: <fill>
Tester: <name>        Date: <date>        Time box: 30 min

AREAS TO COVER (ideas, not a script)
- <area or flow>
- <area or flow>
- <variation: slow network, interruption, odd input, large text>

OUT OF BOUNDS
- <what this session ignores>

NOTES (write while testing, with time)
 hh:mm  <did / saw / thought>
 hh:mm  <did / saw / thought>

FINDINGS
| # | Type (bug / question / idea) | What happened | Steps (short) | Severity |
|---|------------------------------|---------------|---------------|----------|

SESSION SUMMARY
Time split (rough %):  testing __   bug writing __   setup __
Coverage: <what you covered / did not cover>
Next charter: <proposal>

Example (illustrative)

CHARTER
Mission:  Explore the photo upload in the profile
          with large, small and broken image files
          to discover crashes and unclear error messages

Build / device / OS: build 87, mid-range phone, Android 13
Time box: 30 min

AREAS TO COVER
- Pick from gallery, take with camera
- Cancel half way, then retry
- Switch to airplane mode while uploading

OUT OF BOUNDS
- Anything outside the profile screen

NOTES
 00:05  Large image: 20 s spinner, no progress info
 00:14  Cancel during upload: avatar shows old picture, good
 00:22  Airplane mode: the app shows "Error" with no hint

FINDINGS
| 1 | question | Is 20 s for a large file acceptable? | | |
| 2 | bug      | Upload error text is only "Error"    | upload, airplane mode | Medium |

How to adapt it

• Write missions from risks, not from features: "what could go wrong here?"
• Keep missions small. If you cannot finish in 30 minutes, split it.
• Use personas as a resource: "a first-time user with a slow phone".
• Hand it to non-QA testers. The mission line is enough direction; ask for notes with timestamps.
• Turn findings into tests. A bug that hurt goes onto the regression list.

Related

• Hub: Mobile app testing checklist hub
• Bug severity and priority matrix
• Known issues list for testers

Start here and get fresh eyes on your app, with private, structured feedback.