QA and Test Automation Roadmap: Manual Testing to SDET

What QA and test engineers do

Quality assurance (QA) engineers make sure software works before users find the problems. They plan tests, find and report bugs, check that fixes work and increasingly write automated tests that run every time code changes. QA is a common entry point into the industry for freshers, and a strong one: you learn the product, the users and the development process from the inside.

Role ladder:

1. Manual tester / QA analyst: test cases, exploratory testing, bug reports
2. Automation engineer: automates the regression suite with code
3. SDET (Software Development Engineer in Test): builds frameworks and tools, closer to a developer
4. QA lead / test architect: strategy, quality metrics, team leadership

Phase 1: testing fundamentals (weeks 1–4)

• The software testing life cycle and where testing fits in agile teams
• Test levels: unit, integration, system and acceptance testing
• Test design techniques: equivalence partitioning, boundary value analysis, decision tables
• Writing clear test cases and test plans
• Bug reporting: a good report has steps to reproduce, expected and actual results, environment, severity and evidence (screenshot, log)
• Tools: Jira for tracking, TestRail or similar for test cases

Practise by testing real apps and websites. Find five bugs on a popular site and write them up properly.

Phase 2: technical foundations (weeks 4–12)

Even manual testers benefit from technical skills.

• SQL to verify data (SQL guide)
• Browser DevTools: inspect elements, network calls and console errors
• API testing with Postman: requests, assertions, collections, environments
• Git basics (guide)
• Basic Linux commands and reading logs

Phase 3: learn to code for automation (weeks 8–18)

Choose one language: Java or Python are the most requested; JavaScript/TypeScript is the choice for Playwright and Cypress.

• Variables, loops, functions, OOP, collections and exceptions (Java, Python)
• Writing small programs and unit tests

Phase 4: automation tools (weeks 14–28)

• UI automation: Selenium WebDriver (with TestNG or JUnit, or PyTest) is still widely required; Playwright and Cypress are modern, faster alternatives
• Locators, waits, page object model, data-driven tests, handling dynamic elements
• API automation: REST Assured (Java), Requests with PyTest (Python), or Postman with Newman
• CI integration: run tests in Jenkins or GitHub Actions and publish reports
• BDD with Cucumber if your target employers use it

Build a framework from scratch: base class, page objects, configuration, reporting and logging.

Phase 5: beyond functional testing (weeks 24+)

• Performance testing: JMeter or k6, load vs stress, reading results
• Security testing basics: the OWASP Top 10 (cyber security roadmap)
• Mobile testing: Appium basics, device and OS coverage
• Accessibility testing: keyboard use, screen readers, contrast

Projects for your portfolio

1. A Selenium or Playwright framework that tests a public demo e-commerce site, with page objects and an HTML report
2. An API test suite against a public API with automatic checks and CI
3. A test strategy document for a sample app: scope, risks, test types and automation plan

Put them on GitHub with clear instructions.

Interview topics

• Test case design on the spot: "How would you test a login page? A lift? A search box?"
• Difference between severity and priority, smoke vs sanity vs regression testing
• Bug life cycle and how you handle a disputed bug
• Selenium: waits, locators, handling pop-ups and frames, page object model
• API testing: status codes and validation
• Basic coding problems such as reversing a string or finding duplicates (DSA study plan)

Next steps

Keep growing your coding skills to move towards SDET or developer roles (software developer roadmap). You can find current fresher and experienced QA openings on this site.