30 / 71 · 11 Manual Testing Fundamentals · Session Reports← prev⊞ allnext →☰ Read as one page
4.5Aggregating Session Reports
Individual session reports become powerful when aggregated across a release cycle.
Coverage Matrix
Track which areas have been explored and which have not:
| Feature Area | Sessions | Bugs Found | Risk Level | More Testing? |
|---|---|---|---|---|
| File upload | 3 | 5 | High | Yes — bulk upload untested |
| User profiles | 2 | 1 | Low | No — good coverage |
| Checkout flow | 1 | 3 | High | Yes — international payments untested |
| Admin panel | 0 | 0 | Unknown | Yes — not explored at all |
Metrics Over Time
Track across sprints:
- Session count per sprint: is exploratory testing happening consistently?
- Bugs per session: are testers finding issues (good) or exploring already-stable areas (reallocate)?
- Questions generated: are specification gaps being identified?
- Follow-up charter completion rate: are recommended follow-ups actually executed?