Manuals / Test Automation / Guide 1

Start · beginner · ~25 min · Guide 1 of 12

How to use this roadmap

This is a strategy-first curriculum, not a tool tutorial. You will learn how to think like an automation engineer before you pick Playwright, Cypress, or Selenium. Follow the order, pass checkpoints, and build a public strategy repo employers can review.

Path progress
2%

Step 1 of 4

Study pace

Plan 1–1.5 hours most days (≈ 7–10 hrs/week). Accelerated learners at 2–3 hrs/day can finish in ~5–6 weeks. Busy schedule? Stretch to 12–14 weeks — consistency beats speed.

  • Recommended: ~8–10 weeks at 7–10 hrs/week
  • Accelerated: ~5–6 weeks at 2–3 hrs/day
  • Slow track: ~12–14 weeks — still valid
Study paceDrag 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 →Study pacedrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Do this now

Block calendar slots for the next 7 days. Write your target finish date in a README.

Was this step clear?
Chapter learning outcomes
  • How to pace 8–10 weeks part-time
  • Why strategy beats tool-hopping
  • What job-ready means for automation strategy roles

Clear these before you leave

Side quest

Day zero setup

Create the repo, add README with goal and timeline, make the first commit. Install nothing yet except Git and an editor.