# Exploratory Testing Quick Reference

## Charter Format

```
Explore [target] with [resources] to discover [information]
```

## SFDPOT Heuristic

| Letter | Area | Example Focus |
|--------|------|---------------|
| S | Structure | UI, navigation, layout |
| F | Function | Features, behavior |
| D | Data | Valid, invalid, bounds, empty |
| P | Platform | Browsers, OS, devices |
| O | Operations | Install, upgrade, config |
| T | Time | Delays, timeouts, concurrency |

## SBTM Session Flow

```
Charter → Timer → Explore (try, observe, note) → End → Debrief
```

## Session Notes Template

```
Charter: ...
Time: ...
Tester: ...

Exploration: [what you did, what you saw]
Bugs: [list]
Risks: [concerns]
Next charters: [ideas]
```

## Bug Report Checklist

- [ ] Title (one line)
- [ ] Steps to reproduce (numbered)
- [ ] Expected vs actual
- [ ] Environment (browser, OS)
- [ ] Screenshots/video (when helpful)

## Debrief Outline

- Findings (bugs, risks)
- Coverage (what was/wasn't tested)
- Next charters
- Blockers

## Exploratory vs Scripted

| Exploratory | Scripted |
|-------------|----------|
| Learn + design + execute | Follow predefined steps |
| Discovery, unknowns | Regression, known risks |
| Charters guide | Test cases define |
| Debrief shares learning | Results are pass/fail |

## One-Liners

- **Charter**: Guide, don't prescribe.
- **SFDPOT**: Don't skip Platform, Time, or Operations.
- **Debrief**: Turn exploration into team learning.
- **Combine**: Exploratory finds gaps; automation locks in coverage.