Manuals / Test Automation / Chapter 2

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

Testing vs automation mindset

Manual testing explores. Automation repeats certainty. This chapter builds the judgment to know which tool to pick — and why “automate everything” is a trap that burns teams.

Path progress
10%

Step 1 of 4

Separate discovery from repetition

Exploration finds bugs and questions. Automation locks in answers you already trust. If you automate while still discovering, you freeze the wrong behavior.

Separate discovery from repetitionDrag 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 →Separate discoverydrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Write two columns: “I still need to learn…” and “I need this checked every commit.” Move items ruthlessly.

Pro tip: If a flow changes weekly, automate the stable core — not the fashion.

Was this step clear?
Chapter learning outcomes
  • The job of testing vs the job of automation
  • When automation pays for itself
  • How to talk about risk without jargon

Clear these before you leave

Side quest

Risk map

For a demo login page, list 8 risks. Circle the 3 worth automating first. Share why the other 5 wait.