Pathwise

Manuals / Test Planning & Strategy / Chapter 3

A · Strategy · intermediate · ~35 min · Chapter 3 of 9

Strategy: levels & types

Unit, integration, API, UI, exploratory, a11y, security, performance — choose the cheapest level that finds the risk.

Path progress
33%

Step 1 of 1

Level map

For your feature, assign risks to levels. Avoid “everything in E2E.”

  • Unit — logic & pure functions
  • API/contract — integrations
  • UI E2E — critical journeys only
  • Exploratory — unknowns & UX
  • Prod checks — monitoring / synthetics
Level mapDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Level mapdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Draw a simple pyramid/map with example tests at each level.

Was this step clear?
Chapter learning outcomes
  • Test pyramid judgment
  • Shift-left/right
  • Who owns what

Clear these before you leave