Write exploratory testing charters

An hour of manual testing on a new feature, and you want it structured.

Write exploratory testing charters for the feature below.

Each charter: "Explore [area] with [resources or technique] to discover [type of information]", plus a suggested time box of 30 to 60 minutes.

Produce six to eight charters covering different angles: the intended flow, interrupted and abandoned flows, unusual data, permissions and roles, the boundary with other features, recovery after failure, and behaviour on a slow or flaky connection.

For each charter add: what a problem would look like in this area, and what to record while testing.

Then name the two areas most likely to hide defects given what I have told you, and say why. Do not turn these into scripted step-by-step cases, the value is in the freedom.

Feature:

Beyond unit tests. Manual QA, exploratory charters, accessibility, load, and contracts between services.