🧪 Testing & QA · role roadmap · updated for 2026

QA Engineer Roadmap

QA engineers make sure software works before users find out it doesn't, and automation skills have made the role one of the most in-demand in tech. This free QA engineer roadmap starts with software quality assurance and manual testing, then API testing with Postman, UI automation with Selenium, Cypress and Playwright, running tests in CI, and using AI to test faster — including how to test AI features themselves.

33steps in 6 stages
32free lessons · 133 min read
~200 hstudy & practice
4–7 monthsBeginner → Job-ready
0%
Your progress
0 of 32 lessons
Saved in this browser — no account needed.
Next up · step 1 Software Quality Assurance Basics → 🎉 Every lesson done — take a Skill Forge test below!
By the end you'll be able to:
  • ✔Plan testing with the STLC, risk-based priorities and clear exit criteria
  • ✔Design test cases with EP, BVA, decision tables and state transitions
  • ✔Write bug reports developers can act on immediately
  • ✔Automate API tests with Postman/Newman and UI tests with Selenium, Cypress and Playwright
  • ✔Run suites in CI, fix flaky tests, and use AI safely in testing

The roadmap

1
Stage 1 of 6 · 4 steps

QA foundations

  1. What SQA is, how QA, QC and testing differ, the seven testing principles and what a QA engineer does all day.

    Start lesson →
  2. Where testing fits in Waterfall, Agile and Scrum, the six STLC phases, entry and exit criteria, and shift-left testing.

    Start lesson →
  3. Unit, integration, system and acceptance testing, functional vs non-functional testing, and the test pyramid.

    Start lesson →
  4. How HTTP requests and responses work, how TLS secures HTTPS, and what HTTP/2 and HTTP/3 (QUIC) improve.

    Start lesson →
Stage 1 project · add it to your portfolio

Test strategy for a real app

Pick a public site (an online bookstore or food delivery app) and write a one-page test strategy: scope, risks, test levels and exit criteria.

2
Stage 2 of 6 · 6 steps

Manual testing

  1. What manual testing is, when it beats automation, and how to write clear test scenarios and test cases.

    Start lesson →
  2. Equivalence partitioning, boundary value analysis, decision tables and state transition testing with worked examples.

    Start lesson →
  3. Charters, time-boxed sessions, test heuristics and note-taking for finding the bugs scripted tests miss.

    Start lesson →
  4. Writing bug reports developers can act on, severity vs priority, and every state in the defect life cycle.

    Start lesson →
  5. The difference between smoke, sanity and regression testing, building a regression suite and testing a release.

    Start lesson →
  6. SQL for Testers Optional 4 min

    SELECT, WHERE, comparison and logical operators, LIKE, IN, BETWEEN, ORDER BY, and LIMIT.

    Start lesson →
Stage 2 project · add it to your portfolio

Test suite + bug portfolio

Write 30 test cases for its signup and checkout using EP, BVA and a decision table, run two exploratory sessions, and publish five well-written bug reports.

3
Stage 3 of 6 · 5 steps

API testing

  1. The 2xx-5xx status code families, the codes that matter most, and key HTTP headers.

    Start lesson →
  2. Sending your first API requests, organising collections, and using environments for dev, staging and production.

    Start lesson →
  3. pm.test and pm.expect assertions on status codes, headers, bodies and response times, plus pre-request scripts.

    Start lesson →
  4. Variable scopes, saving a login token for later requests, and chaining create → read → update → delete flows.

    Start lesson →
  5. Validating responses against a JSON Schema in Postman so a changed API contract fails a test immediately.

    Start lesson →
Stage 3 project · add it to your portfolio

Postman collection for a public API

A collection for DummyJSON with login, chained CRUD requests, schema validation and negative tests — exported to GitHub.

4
Stage 4 of 6 · 8 steps

UI automation

  1. What to automate (and what not to), the test automation pyramid, choosing a tool and calculating automation ROI.

    Start lesson →
  2. What JavaScript is, where it runs (browser and Node.js), and how the language has evolved since ES2015.

    Start lesson →
  3. Selenium WebDriver Optional 4 min

    Your first Selenium test in Python — locators, actions, explicit waits and assertions against a real login form.

    Start lesson →
  4. Structuring UI tests with page objects so a changed selector is a one-line fix, with a full pytest example.

    Start lesson →
  5. Playwright 4 min

    Installing Playwright Test, running your first cross-browser test, and recording tests with codegen.

    Start lesson →
  6. Role-based locators, web-first assertions and why Playwright tests rarely need manual waits.

    Start lesson →
  7. Cypress Optional 4 min

    Installing Cypress, the Test Runner, and writing your first end-to-end test against a real page.

    Start lesson →
  8. Testing REST APIs with the request fixture and mocking backend responses with page.route.

    Start lesson →
Stage 4 project · add it to your portfolio

Playwright framework

A Playwright + TypeScript project with page objects, fixtures, a stored login state and 15 tests covering positive, negative and mocked-error flows.

5
Stage 5 of 6 · 5 steps

Ship with confidence

  1. Creating branches, fast-forward vs merge commits, and resolving a merge conflict.

    Start lesson →
  2. Running one test against many inputs with pytest parametrize, and writing Gherkin scenarios with pytest-bdd.

    Start lesson →
  3. Running automated tests in GitHub Actions, headless browsers, reports, and finding and fixing flaky tests.

    Start lesson →
  4. Newman in CI 4 min

    The Collection Runner with CSV data files, and running collections from the command line and CI with Newman.

    Start lesson →
  5. Defect density, leakage, test coverage, pass rate, MTTR and how to write a test summary report people read.

    Start lesson →
Stage 5 project · add it to your portfolio

CI pipeline with reports

Run the UI suite and Newman API tests in GitHub Actions on every pull request, with HTML reports, traces on failure and zero flaky tests.

6
Stage 6 of 6 · 5 steps

AI & the future of QA

  1. Where AI genuinely helps QA teams today, where it does not, and how to use it without losing test quality.

    Start lesson →
  2. Prompts that turn requirements into test cases and test data, and the review checklist that keeps them correct.

    Start lesson →
  3. Testing non-deterministic AI features — golden datasets, property assertions, LLM-as-judge and safety tests.

    Start lesson →
  4. Performance Testing with k6 Optional Coming soon

    We're writing this lesson — learn it in a mentor-led program meanwhile.

  5. Manual testing interview questions — test cases, design techniques, bugs and real scenarios — with answers.

    Start lesson →
Stage 6 project · add it to your portfolio

Evaluate an AI feature

Build a golden dataset of 20 cases for a summariser or chatbot, add property assertions and five prompt-injection tests, and report the pass rate.

🏁

Finish line: prove it

Finished the roadmap? Turn it into proof employers trust.

🏆 Earn a free Skill Forge certificate

🧭 Where to go next

QA Engineer Roadmap FAQ

Do I need to know programming to become a QA engineer?
You can start in manual testing without coding, but automation is now expected in most QA roles. Learn basic JavaScript or Python alongside manual testing — this roadmap adds programming at the UI automation stage.
Should I learn Selenium, Cypress or Playwright?
Learn Playwright first for new projects — it is fast, reliable and covers all browsers. Learn Selenium too if you target companies with existing Selenium suites, and Cypress if you join a JavaScript front-end team. The concepts transfer between all three.
How long does it take to become a QA engineer?
Most learners become job-ready for junior QA roles in 4–7 months with 1–2 hours a day. A GitHub portfolio with a Postman collection, a Playwright framework and a CI pipeline makes the biggest difference in interviews.
Will AI replace software testers?
AI is changing testing, not removing it. It speeds up drafting test cases and writing automation, but someone still has to understand the risks, judge correctness and test AI features themselves — which is a fast-growing skill.

Keep going after this roadmap

See all 14 roadmaps →