Automation testing roadmap at a glance
This is a month-by-month plan for a part-time learner starting from zero. It covers about 6 months at 10–12 hours a week. Every stage gives you something you can show — a test plan, a working script, a framework or a CI pipeline.
| Month | Learn | Practise / Build | Milestone you can show |
|---|---|---|---|
| Month 1 | Manual testing foundations: SDLC/STLC, test design, bug reporting, JIRA | Write test cases, log bugs and track them in JIRA | Test plan and bug report for a sample app |
| Month 2 | Programming for testers — Java or JavaScript/TypeScript | Write small scripts, run them from the terminal, push to GitHub | GitHub repo with clean code and a README |
| Month 2–3 | SQL for testers | Query a sample database to verify data and set up test data | SQL queries used for test verification |
| Month 3–4 | UI automation — Selenium 4 with TestNG, or Playwright Test | Write 15–20 UI tests against a public demo site | Working UI test suite that passes locally |
| Month 4 | Framework design — POM, data-driven, reporting, logging | Refactor tests into a structured framework | Framework with page objects, data files and reports |
| Month 5 | API testing — Postman, then REST Assured or Playwright API | Add API tests alongside UI tests and chain setup calls | Combined UI + API test suite |
| Month 5–6 | Git, CI/CD (GitHub Actions/Jenkins), running tests in pipelines | Run the suite on every push, upload reports as artefacts | Green CI pipeline with test reports |
| Month 6 | AI-assisted testing tools used responsibly | Use AI tools for test generation and debugging, verify every suggestion | Notes on what AI helped with and what it got wrong |
| Month 6 | Two GitHub frameworks + interview prep | Polish two repos, write docs, prepare interview answers | Two public repos with README and CI badges |
Manual testing foundations (SDLC/STLC, test design, bug reporting, JIRA)
Automation without testing fundamentals produces fast, wrong tests. This stage teaches you how to design a test, what makes a bug report useful and how work flows through a real QA team.
| Topic | What to cover |
|---|---|
| SDLC and STLC | Software development life cycle, software testing life cycle, where testing fits |
| Test design | Equivalence partitioning, boundary value analysis, decision tables, test case structure |
| Bug reporting | Reproducible steps, expected vs actual, severity vs priority, screenshots and logs |
| JIRA | Creating issues, workflows, linking test cases, sprint boards |
| Agile testing | Testing inside sprints, definition of done, regression scope |
Free official resources: ISTQB glossary (free), Atlassian JIRA documentation, Ministry of Testing resources.
Mini project: Pick a public demo app and write a test plan with 15 test cases, then log 5 bugs in JIRA with reproducible steps.
Programming for testers — Java or JavaScript/TypeScript
Automation is code. This stage teaches you enough programming to read, write and debug test scripts — not to become a software developer.
| Topic | What to cover |
|---|---|
| Language choice | Java or JavaScript/TypeScript — which fits the job market you are targeting |
| Language basics | Variables, data types, conditionals, loops, functions, arrays, objects |
| Object-oriented basics (Java) | Classes, objects, inheritance, interfaces — enough to read a framework |
| Async and promises (JS/TS) | async/await, promises, callbacks,
handling errors |
| Tooling | IDE setup, build tools (Maven/Gradle or npm), running scripts from the terminal |
| Git basics | Commits, branches, pull requests, README files |
Free official resources: Java documentation (Oracle), MDN Web Docs for JavaScript, TypeScript handbook, GitHub Skills for Git.
Mini project: Write a small script that reads data from a CSV, performs a calculation and writes the output to another file. Commit it to GitHub with a README.
SQL for testers
Most applications store their truth in a database. This stage teaches you how to check that data and set up test data without waiting for a developer.
| Topic | What to cover |
|---|---|
| Basic queries | SELECT, WHERE, ORDER BY, LIMIT |
| Joins | INNER JOIN, LEFT JOIN, when to use each |
| Aggregations | GROUP BY, HAVING, COUNT, SUM, AVG |
| Data setup | INSERT, UPDATE, DELETE for test data, cleaning up after tests |
| Constraints and keys | Primary keys, foreign keys, unique constraints — why they matter for tests |
Free official resources: PostgreSQL documentation, MySQL documentation, SQLBolt, Mode SQL tutorial.
Mini project: Load a sample dataset into a local database and write queries to verify five application rules (for example, every order has a customer).
UI automation — Selenium 4 with TestNG, or Playwright Test
This is where you write your first browser automation. Pick one tool and go deep — the concepts transfer if you switch later.
| Topic | What to cover |
|---|---|
| Setup | Installing Selenium WebDriver or Playwright, browser drivers, project setup |
| Locators | ID, name, CSS selectors, XPath (Selenium) or role-based locators (Playwright) |
| Waits | Explicit waits and expected conditions (Selenium) or auto-waiting assertions (Playwright) |
| Test runner | TestNG annotations and assertions (Selenium) or Playwright Test
with test() and expect() |
| Common actions | Clicks, typing, selecting dropdowns, file uploads, alerts, frames, tabs |
| Assertions | Element visible, text matches, URL correct, error messages shown |
Free official resources: Selenium documentation, TestNG documentation, Playwright documentation (Getting Started, Locators, Assertions).
Mini project: Write 15–20 UI tests against a public demo app covering login, search, form submission and error states.
Framework design — POM, data-driven, reporting, logging
A folder of scripts is not a framework. This stage teaches the structure that makes tests reusable, readable and maintainable.
| Topic | What to cover |
|---|---|
| Page Object Model | Page classes, methods, keeping locators inside pages |
| Data-driven testing | External data files, parameterisation, running the same test with multiple data sets |
| Configuration | Environment configs, base URLs, credentials, .env handling |
| Reporting | Extent, Allure, or Playwright HTML report — pass/fail, screenshots on failure |
| Logging | Log4j or similar for Selenium; built-in logs or custom loggers for Playwright |
| Folder structure | pages/, tests/, data/, utils/, reports/ — why a consistent layout matters |
Free official resources: Selenium documentation (Page Object Model), Playwright documentation (POM pattern, Fixtures), Allure documentation.
Mini project: Refactor your Stage 4 tests into a framework with page objects, a data file and an HTML report.
API testing — Postman, then REST Assured or Playwright API
Many bugs live below the UI. This stage teaches you how to test APIs directly and how to use API calls to set up state for UI tests.
| Topic | What to cover |
|---|---|
| HTTP basics | Methods, status codes, headers, request and response bodies |
| Postman | Collections, environments, variables, chained requests, assertions |
| REST Assured (Java) | Given-when-then syntax, JSON path assertions, schema validation |
| Playwright API (JS/TS) | Request context, sending requests, asserting on responses |
| API + UI together | Creating test data via API, then verifying in the UI |
Free official resources: Postman Learning Center, REST Assured documentation, Playwright documentation (API testing).
Mini project: Add a set of API tests to your framework and use one of them to create test data for a UI test.
Git, CI/CD (GitHub Actions/Jenkins), running tests in pipelines
A test suite that only runs on your laptop is half a framework. This stage teaches you how to run tests on every commit and publish the results.
| Topic | What to cover |
|---|---|
| Git workflows | Feature branches, pull requests, merge conflicts, tags |
| GitHub Actions | Workflow files, running tests on push and PR, caching dependencies |
| Jenkins | Pipeline basics, running Selenium or Playwright in Jenkins, publishing reports |
| Artefacts | Uploading reports, screenshots and logs as build artefacts |
| Secrets | Storing credentials and API keys in CI, environment variables |
Free official resources: GitHub Actions documentation, Jenkins Pipeline documentation, Git documentation.
Mini project: Run your framework on every push with GitHub Actions and upload the test report as an artefact.
AI-assisted testing tools used responsibly
AI tools can speed up test generation and debugging, but they can also produce confident wrong answers. This stage teaches you how to use them without lowering quality.
| Topic | What to cover |
|---|---|
| Where AI helps | Generating boilerplate tests, explaining stack traces, summarising failures |
| Where AI fails | Hallucinated selectors, outdated APIs, missing business context |
| Review discipline | Reading every generated line, running the test, checking it fails for the right reason |
| Privacy | Not pasting proprietary code or test data into public AI tools |
| Tooling | AI assistants in IDEs, AI-powered test generators, when to use them |
Free official resources: Vendor documentation for AI coding assistants, OWASP guidance on AI risks.
Mini project: Use an AI tool to draft five tests for a page, then review and fix them. Write a short note on what it got right and wrong.
Two GitHub frameworks + interview prep
The final stage turns learning into a portfolio. Two well-structured frameworks on GitHub are worth more than a list of certificates.
| Item | What it involves |
|---|---|
| Framework 1 | Selenium with TestNG — POM, data-driven, reporting, CI |
| Framework 2 | Playwright with TypeScript — fixtures, API tests, CI |
| Documentation | README with setup steps, folder structure, how to run tests and what the suite covers |
| CI badges | A visible green pipeline badge in each README |
| Interview prep | Explaining framework choices, locator strategy, flaky test fixes and CI setup |
Interview prep: Be ready to walk through your folder structure, your locator strategy, one flaky test you fixed and how your CI pipeline works. Expect questions on waits, POM, API testing and when to use Selenium vs Playwright.
Projects to build along the way
Each stage produces one artefact. By the end, these projects are your portfolio — they prove you can build and maintain automation frameworks, not just write isolated scripts.
| Stage | Project | Tools | What it proves |
|---|---|---|---|
| Stage 1 | Test plan and bug report | JIRA, test design techniques | You can design tests and write reproducible bug reports |
| Stage 2 | Programming practice repo | Java or TypeScript, Git | You can write and debug code |
| Stage 3 | SQL verification queries | PostgreSQL or MySQL | You can verify data and set up test data |
| Stage 4 | First UI test suite | Selenium + TestNG or Playwright | You can automate browser flows reliably |
| Stage 5 | Structured framework | POM, data files, reports | You can build a maintainable framework |
| Stage 6 | API test suite | Postman, REST Assured or Playwright API | You can test APIs and combine them with UI tests |
| Stage 7 | CI pipeline | GitHub Actions or Jenkins | You can run tests on every commit |
| Stage 8 | AI-assisted testing notes | AI coding assistants | You can use AI tools without lowering quality |
| Stage 9 | Two GitHub frameworks | All of the above | You can build and maintain complete automation frameworks |
Fast-track vs part-time plan
The roadmap is the same either way — only the pace changes. Choose the plan that fits your available hours, not the one that looks impressive.
| Plan | Weekly effort | Estimated months | Best for |
|---|---|---|---|
| Fast-track | 20+ hours a week | 3–4 months | Full-time learners, career switchers with free time |
| Part-time | 10–12 hours a week | 5–6 months | Working professionals, students with college |
Automation Testing roadmap for different backgrounds
Fresher (any degree)
Start with manual testing and programming if you have never coded. Then follow all nine stages. Your two GitHub frameworks matter more than your degree — build them early and keep improving them.
Non-IT / commerce background
Spend extra time on Stage 2 (programming). Use manual testing and API testing with Postman to build confidence early. Strong frameworks can open doors without a CS degree.
Working professional
Go part-time (10–12 hours a week). Compress Stage 1 if you already know testing basics. Focus on Stages 4–9 and ship two complete frameworks rather than scattered scripts.
Career-gap returner
Treat the two GitHub frameworks as your re-entry proof. Include READMEs with setup steps, CI badges and test reports. Add a short write-up of what you learned at each stage.
Selenium or Playwright first?
Both tools are worth knowing. Which one to learn first depends on your language preference, the kind of company you are targeting and what you already know.
| Factor | Choose Selenium first if… | Choose Playwright first if… |
|---|---|---|
| Preferred language | You already know Java or plan to work in Java-heavy enterprises | You prefer JavaScript or TypeScript and want a modern language stack |
| Job market type | You are targeting large IT services or legacy enterprise projects | You are targeting product companies, startups or newer QA teams |
| Existing skills | You have used Selenium before or your team already uses it | You have used Playwright, Cypress or modern JS tooling |
| Learning curve | More setup — drivers, waits, test runner configuration | Faster setup — auto-waiting and a built-in test runner |
| API testing | REST Assured is a separate library you add | Built-in request context for API tests |
| CI integration | Well-documented with Jenkins and Maven | Well-documented with GitHub Actions and npm |
Common mistakes on this roadmap
- Skipping manual testing — you cannot automate what you cannot test by hand.
- Skipping programming — copying scripts from tutorials breaks the moment the app changes.
- Using brittle locators (long XPath) when stable IDs or roles exist.
- Hard-coding sleeps instead of explicit waits or auto-waiting assertions.
- Ignoring CI — a suite that only runs locally is not a framework.
- Collecting certificates instead of shipping two GitHub frameworks.
Jobs you can apply for at the end
At the end of this roadmap you can apply for Automation Test Engineer, SDET and QA Automation roles. Indeed reports an average Automation Test Engineer salary of ₹6,17,659 (93 salaries, updated 1 Oct 2026) and an average Software Test Engineer salary of ₹9,17,316 (296 salaries, updated 3 Oct 2026).
| Role | Salary figure | Source and date |
|---|---|---|
| Automation Test Engineer | Average ₹6,17,659; Bengaluru ₹13.90L, Gurgaon ₹9.05L, Chennai ₹8.15L, Noida ₹7.10L, Pune ₹6.64L | Indeed, 93 salaries, updated 1 Oct 2026 |
| Software Test Engineer | Average ₹9,17,316; Mumbai ₹15.19L, Noida ₹14.83L, Gurgaon ₹11.30L, Hyderabad ₹10.71L, Pune ₹10.67L | Indeed, 296 salaries, updated 3 Oct 2026 |
Follow this roadmap with a trainer
Uncodemy's Software Testing program covers manual testing, SQL, API testing and Selenium automation — the core of this roadmap. The separate Playwright Automation program covers JavaScript and Playwright for the modern stack.
| Program | Details |
|---|---|
| Software Testing | Software Testing — ₹17,500 + GST, 4–5 months. Manual + SQL + API + Selenium automation. |
| Professional Certificate Program in Playwright Automation | Playwright Automation — JavaScript, Playwright, Mocha, API testing, Jenkins, GitHub, Allure, GitHub Copilot; 5 domain projects. Fee and duration unverified. |
| Automation Testing | Automation Testing — Selenium WebDriver with Java, TestNG, Maven, Jenkins, POM/hybrid frameworks, Cucumber. Fee and duration unverified. |
Ready to explore? Book a free counselling session, try a 2-class trial or use the AI-powered career guidance tool.