Pathwise

Manuals / Test Automation / Chapter 3

A · Foundations · beginner · Week 1–2 · Chapter 3 of 12

The test pyramid in practice

The pyramid is a budget. Most checks should be fast and close to logic. A few UI journeys prove the seams. This chapter turns the diagram into daily decisions and written policy.

Path progress
19%

Step 1 of 4

Draw your real pyramid

Ideal pyramids are rare. Start with what you have, then rebalance. Count tests by layer and by runtime.

Draw your real pyramidDrag 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 →Draw your real pyrdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Sketch three layers. Estimate count and minutes for each. Circle the top-heavy parts.

Was this step clear?
Chapter learning outcomes
  • Unit, integration, API, UI tradeoffs
  • How to spot duplicate coverage
  • Smoke vs deep suites

Clear these before you leave

Side quest

Pyramid memo

One page: current pyramid, ideal pyramid, 3 rebalancing moves this month. Commit to your repo as PYRAMID.md.