2. Testing vs automation mindset
Test Automation · 48 pages source format
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.
What you'll learn
- The job of testing vs the job of automation
- When automation pays for itself
- How to talk about risk without jargon
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.
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.
Cost of a check
Every automated check has write cost, wait cost, and flake cost. UI checks are the most expensive. Prefer fast feedback closer to the code when you can.
Do this now
Pick one product feature. List 5 checks. Label each Unit / API / UI. Defend one label out loud.
Define “done” for an automated test
A good test fails for the right reason, reads like a story, and leaves an artifact (log, screenshot, trace) when it fails.
Do this now
Write a one-sentence acceptance for your first future test: “Given… when… then…”
Manual skills still matter
Automation engineers who cannot explore manually write brittle scripts. Your manual charter (exploratory notes, charters, session sheets) feeds what to automate.
Do this now
Spend 30 minutes exploring Sauce Demo manually. Write 10 observations automation would miss on first pass.