3.3The SBTM Framework

SBTM provides three core elements: charters, sessions, and debriefs.

Charters

A charter is a mission statement for your testing session. It answers: "What am I testing, and why?"

Good charters are specific and bounded:

Explore the checkout flow with international addresses
to discover currency conversion and tax calculation issues.

Explore the file upload feature with edge-case formats (.svg, .webp, 0-byte files)
to discover handling gaps and silent failures.

Explore the admin user management panel under concurrent usage
to discover race conditions in role assignment.

Bad charters are vague:

• "Test the login page" (too broad — what are you looking for?)
• "Find bugs" (not a charter — it is a wish)
• "Test everything in the settings module" (no focus, no time boundary)

Writing Effective Charters

Use the formula: Explore [target] with [resources/approach] to discover [information].

Component	Description	Example
Target	The feature or area to test	Checkout flow
Resources/Approach	Specific data, tools, or techniques	International addresses, edge-case payment methods
Information	What kind of issues you are looking for	Currency conversion errors, tax miscalculations

Prepare 2-3 charters before a session. If you finish one early, move to the next. If you discover something unexpected, pivot — but document the pivot.