How to use the Automation Tester Roadmap
- 1. Tick what you knowOpen each stage and tick the topics you can already do confidently.
- 2. Pick your paceChoose how many hours a week you can study; the estimate updates for what's left.
- 3. Get your planSee time left per stage and your next three topics, and download the checklist.
Who this roadmap is for
Automation testers write code that checks software works, so teams can release often without breaking things. This roadmap starts with manual testing fundamentals, because automating a poorly designed test just makes a bad test run faster.
It lets you pick Selenium or Playwright. Both are widely used; the framework ideas (page objects, data-driven tests, reports, CI) are the same.
The 8 stages
Each of the 8 stages of the Automation Tester path ends with a milestone project, because building something is what turns topics into skills.
- Testing fundamentals (about 2 weeks): SDLC and STLC, Test levels and types: unit, integration, system, acceptance, Test design: equivalence partitioning, boundary values and more. Milestone: Test plan and 30 test cases for a login and signup flow.
- Programming for testers (about 4 weeks): Java or Python basics, OOP: classes, inheritance, interfaces, Collections and exceptions and more. Milestone: Small programs that read test data from CSV and JSON.
- Web UI automation (about 5 weeks): Locators: CSS, XPath, role-based, Selenium WebDriver or Playwright basics, Waits and avoiding flaky tests and more. Milestone: Automate 15 scenarios on a demo e-commerce site.
- Test frameworks (about 3 weeks): TestNG or JUnit / pytest, Assertions, fixtures and data-driven tests, Reports: Allure or Extent and more. Milestone: Framework with data-driven tests and HTML reports.
- API testing (about 3 weeks): HTTP, REST and JSON basics, Postman collections and environments, REST Assured or requests + pytest and more. Milestone: API test suite for a public API with positive and negative cases.
- CI/CD and tools (about 2 weeks): Git and branching for test code, Running tests in GitHub Actions or Jenkins, Docker for test environments and more. Milestone: Pipeline that runs your suite on every push.
- Beyond functional (about 2 weeks): Performance testing basics with JMeter or k6, Accessibility checks, Mobile testing idea with Appium and more. Milestone: Load test one API and report response times.
- Job ready (about 2 weeks): ISTQB Foundation preparation, Framework walk-through for interviews, Interview topics: waits, locators, POM and more. Milestone: Record a demo of your framework running in CI.
How the time estimate works
Worked example: with nothing ticked and 10 hours a week, the plan shows about 23 weeks for all 33 topics. Choose 20 hours a week and it becomes about 11.5 weeks. Tick every topic in the first stage, Testing fundamentals, and that row shows "done" while the total at 10 hours a week drops by 2 weeks to about 21.
Week counts are our suggestion for steady self-study of the Automation Tester path, based on how much each stage covers. They are not survey data or a promise; use them to plan, not to judge yourself.
Tips for following it
- Fix flaky tests immediately; a suite nobody trusts gets ignored.
- Prefer stable, user-facing locators (roles, labels, test IDs) over long XPaths.
- Automate the boring regression checks first, not the rare edge cases.
Frequently asked questions
Java or Python for automation?
Both are common. Java with Selenium and TestNG appears in many job posts; Python with pytest is quicker to learn. Choose one and stick with it.
Is manual testing still needed?
Yes. Exploratory testing finds problems that scripts don't look for, and good test design comes from manual skills.
Where are my ticks saved?
Your Automation Tester Roadmap ticks are kept only in this browser on this device, so nothing you tick is sent anywhere. Clearing site data or switching browsers starts you fresh; download your checklist to keep a copy.
Is the Automation Tester Roadmap free?
Yes. Reading the Automation Tester Roadmap and ticking topics is open to everyone. Viewing your plan the first time asks for your name and WhatsApp number once; after that every Uncodemy tool is free and open to you.