How long does it take to move from manual to automation testing?

With 8 to 10 hours a week most manual testers can write useful automated tests in two to three months and build a small framework with a portfolio project in about six. Your starting programming experience changes this a lot.

Do I need to learn programming first?

Yes, a little. You need variables, conditions, loops, functions, strings, lists and maps, and reading error messages. Two to four weeks of steady practice in one language is enough to start.

Manual to automation testing roadmap: a 6-month plan

This is a plan, not a promise. Timelines depend on your hours, your starting point and the job market in your city. It assumes about 8 to 10 hours a week. If you have less, stretch each month.

Before you start: choose, then stick

Pick one language and one UI tool and stay with them for six months. The choice matters less than finishing.

Many Indian IT services job descriptions ask for Java with Selenium. Fastest check: paste five job descriptions you like into the resume keyword matcher and see which words repeat.
Python with pytest is increasingly asked for, especially for API testing and at product companies, and is the gentlest language to start with. See Python for testers and the practice tutorial.
TypeScript with Playwright is a strong choice for product companies and startups, and has the shorter set-up. See Selenium vs Playwright.
Not sure? Read Java vs Python vs JavaScript for automation and count the languages in ten job descriptions.

Month 1: programming basics

Goal: write small programs without copying.

Variables, data types, conditions, loops, methods.
Strings, arrays or lists, maps. Do the string problems in Java for testers or Python for testers (reverse, palindrome, duplicates).
Reading a stack trace and finding the line that failed.
Git basics: init, add, commit, branch, push to GitHub.

Check: you can write "count the words in a sentence" from a blank file, in 15 minutes.

Month 2: UI automation with one tool

Goal: automate real pages.

Set up the tool and run a first test.
Locators: id, CSS, XPath. Practise with the XPath and CSS tester.
Waiting properly (explicit waits in Selenium, auto-waiting in Playwright). No sleeps.
Forms, dropdowns, alerts, iframes, windows, tables, file upload. Every one of these is on the practice playground.
Assertions with a test runner (TestNG or JUnit; Playwright test).

Check: automate the playground's login, form and table pages, with every test independent and passing five times in a row.

Month 3: API testing

Goal: test the layer under the UI.

HTTP: methods, status codes, headers, authentication (API testing questions).
Postman: requests, variables, environments, test scripts.
Automate API tests in code (Rest Assured for Java, requests with pytest for Python, Playwright's request for TypeScript).
JSON: reading responses and writing assertions with JSONPath (JSON tools).
SQL basics to check data (SQL for testers).

Check: for one endpoint, write ten API tests covering success, validation errors, authentication and boundaries.

Month 4: framework design

Goal: structure that survives growth.

Page Object Model, or fixtures in Playwright.
Test data: created through the API per test, removed afterwards.
Configuration by environment; secrets outside the repository.
Reports, screenshots and traces on failure.
Parallel runs with independent tests.

Check: a teammate can clone your repository, run one command and see a report.

Month 5: CI and the portfolio project

Goal: something real to show.

Run the suite in GitHub Actions on every push.
Pick an application with real bugs and test it end to end: requirements, a test plan, manual cases, automated UI and API tests, and a bug list. The free buggy app exists for this, and the portfolio project kit gives a worked structure and answers. You can also pick any open-source app.
Write a README that explains what you tested, how to run it, what you found and what you would do next.

Check: the repository has a green build badge, a clear README and at least 20 meaningful tests.

Month 6: interviews

Goal: turn the work into offers.

Rewrite your resume with the project at the top: what you tested, tools, result. Use real numbers from your project.
Practise explaining the framework out loud (3 to 5 years questions has the standard follow-ups, even if you are earlier in your career).
Search properly with the job search query builder, and match your resume to each job description.
Revise scenario-based questions and take the quizzes.

Common mistakes

Learning three tools at once and finishing none.
Watching tutorials without typing. Every code sample must be typed and changed.
Copying a framework you cannot explain. In the interview, they ask about the details.
Waiting until you feel ready before applying. Start applying in month 5, while you finish the project.
Dropping manual skills. Good automation comes from good test thinking.

Manual to automation testing roadmap