Sefism QA and Test Automation Roadmap

What this roadmap is

The QA and test automation roadmap is Sefism's path into software quality work, written by Tauseef Fayyaz for students and early-career engineers. It starts with careful manual testing and ends with an automated suite that runs in CI, and it asks you to pick one automation tool at the start: Playwright (TypeScript, the default), Selenium (Java) or API testing (Postman and JavaScript). The fundamentals, manual testing, web basics, CI, non-functional and career stages are shared by all three; the programming and automation stages switch their topics and milestones to match the tool you chose.

By the end you should be able to:

• Turn a user story into test ideas with partitions, boundaries and risk, and run a timed exploratory session with notes.
• Write bug reports with clear steps, evidence and a sensible severity that developers can reproduce in minutes.
• Build an automated suite in your chosen tool, structured with page objects or an API client, that runs in GitHub Actions with a readable report.
• Diagnose and fix flaky tests, and run basic performance, accessibility and security checks safely.
• Show a public portfolio of test suites and bug reports, and apply for QA roles with a clear path towards SDET.

Who it suits, and who should start elsewhere

It suits students who enjoy finding out how things break, graduates who want a realistic first role in software, and developers or support engineers who want to specialise in quality. It does not assume a computer science background, but it does expect you to write real code from stage four onwards: automation engineers are programmers who specialise in testing.

If you have never written a program, begin with the Programming foundations roadmap and come back. If what you really want is to build web products and test them as part of that, the Frontend or Backend roadmaps are a better fit. If security testing is the part that excites you, look at the Cybersecurity roadmap; this roadmap only covers security at awareness level.

Prerequisites and realistic time

You need a laptop that can run a browser, VS Code and Node.js or Java, and the habit of writing things down. The roadmap adds up to about 282 hours across 8 stages. How many weeks that becomes depends on the hours you give it each week:

• At about 5 hours a week (the default on the public page): roughly 57 weeks.
• At about 8 hours a week: roughly 39 weeks.
• At about 12 hours a week: roughly 26 weeks.

The first stage is a foundation stage. If you tell the roadmap you are already comfortable with testing basics, it is skipped; if you know some of it, it becomes a shorter review.

A sample week for a student (10 to 12 hours). Two weekday evenings of two hours on the stage's topics, one evening on the checklist, and a longer weekend block on the milestone. At this pace the whole roadmap fits into about two university semesters.

A sample week for someone working full time (5 hours). Two 45-minute sessions on weekdays for reading and small exercises, and a three-hour block at the weekend for hands-on work on the practice sites. It is slower, but the milestones are designed so that each one is finished work you can show, even before the end.

Stage by stage

1. Testing fundamentals (12 hours, foundation)

What testing is for and the vocabulary every QA conversation uses. Topics: why testing exists, SDLC and STLC, verification and validation, test levels from unit to acceptance, functional and non-functional testing, the test pyramid and risk-based testing. Milestone: a one-page test approach for a real app you use, such as a food delivery or banking app, with its riskiest areas, what you would test at each level, and three functional and three non-functional checks. Tauseef's note here is not to rush to automation: people who struggle as automation engineers usually automate the wrong things.

2. Manual testing done well (30 hours)

Turning requirements into test ideas and bugs into reports that get fixed. Topics include analysing acceptance criteria, partitions, boundaries and decision tables, test cases and checklists, exploratory testing with charters, bug reports, severity and priority, smoke, sanity and regression testing, and test management tools. Milestone: a test pack for one feature of a practice app: 15 to 20 cases or checklist items, notes from two 60-minute exploratory sessions, and five bug reports with evidence. You practise on the-internet and Restful-booker, which contain bugs on purpose.

3. Web and API basics for testers (25 hours)

How browsers and servers talk, and how to question that traffic. Topics: HTTP requests, methods and status codes, browser DevTools, JSON and REST, calling APIs by hand with Postman and curl, sign-in with cookies and tokens, and enough SQL to check the data behind the screen. Milestone: an API exploration report on Restful-booker with 10 requests sent by hand, three bugs with evidence and three SQL queries written on SQLBolt's practice data.

4. Programming for testers (60 hours)

The programming your automation tool needs, in its language: TypeScript for Playwright, Java for Selenium, or JavaScript for API tests. Topics cover conditions, loops and functions, collections, async code or classes depending on your tool, packages, build tools and Git, and assertions with a test runner. Milestone: a GitHub repository of small programs with passing tests, such as a discount rule checked at its boundaries and a function that reads a saved JSON response.

5. Automation in depth (70 hours)

The largest stage, and it changes completely with your choice. Playwright covers user-facing locators, auto-waiting and web-first assertions, fixtures, codegen, UI mode and the trace viewer, network mocking and cross-browser projects. Selenium covers WebDriver, locators, explicit waits, forms, frames and windows, TestNG and JUnit 5, failure evidence and Selenium Grid. API testing covers Postman collections and environments, test scripts and chaining, schema and negative tests, command-line runs, API tests as code and an optional look at contract testing with Pact. Milestone: an automated suite in a public repository covering five important flows from your manual test pack, with real assertions, no fixed sleeps and evidence captured on failure.

6. Maintainable suites in CI (45 hours)

Making the suite cheap to change and trustworthy. Topics: page objects and components (or an API client layer), data-driven tests and test data, flaky tests and their causes, GitHub Actions, parallel runs and sharding, reports and failure evidence, and deciding what runs when. Milestone: your suite refactored and running on every pull request and nightly, in parallel, with an HTML report, uploaded evidence and a short note on one flaky test you found and fixed.

7. Performance, accessibility and security awareness (20 hours)

Going beyond functional checks without pretending to be a specialist. Topics: performance testing basics, a first load test with k6 and where JMeter fits, WCAG basics, automated and manual accessibility checks, security testing awareness, access control tests with two accounts, and a safe first ZAP scan. Milestone: a short non-functional report on your practice app. The rule that never bends: only load test or scan systems you own or have written permission to test.

8. Your QA career (20 hours)

Roles, the ISTQB question, a portfolio and the first job. Topics: QA roles, whether ISTQB Foundation is worth it for you, a portfolio of suites, public bug reports as proof, getting through QA hiring, your first months, and growing towards SDET while avoiding job scams. Milestone: a pinned portfolio repository with a green CI badge, three linkable bug reports, a written decision on ISTQB and ten tailored applications sent.

Projects to build alongside

The roadmap suggests four final year or portfolio projects from the Sefism library:

• QA Test Suite for an Open Source Web App: the portfolio piece employers ask for, with a test plan, bug reports and a suite in CI.
• API Contract Checker for Continuous Integration: schema checks and breaking-change detection on every pull request.
• Web Accessibility Regression Testing in CI: UI automation, axe checks and CI in one tool.
• URL Shortener with Click Analytics and a Load Test Report: build a small service and test it end to end, including a k6 report.

How it works on Sefism

Everything on Sefism is free to learn from. The public roadmap page shows the full list of stages with their summaries and length, and opens the first two stages so you can see how the teaching works. Adding the roadmap to your dashboard opens every stage. Your first roadmap is free to add; after that, adding a roadmap uses credits, and new members get starting credits when they join.

Inside your dashboard, each topic has a short explanation, a question to answer without notes before you move on, and a prompt you can paste into an AI assistant so it quizzes you rather than doing the work. Each stage has Tauseef's advice and curated resources, most have a hands-on checklist, and you tick stages off as you finish them. You also get the companion cheat sheet, and you can ask Tauseef a question about any stage when you are stuck.

The companion cheat sheet

The QA and test automation cheat sheet covers the same ground in short, revisable entries: test design, bug reports, HTTP and SQL, your automation tool, flakiness, CI and the non-functional basics. Its edition follows the tool you chose, and topics in the roadmap link straight to the concepts that cover them.

Related on Sefism

• How to move from QA to software development, if you see QA as a step towards building.
• How to approach a take-home coding assignment, useful for QA take-home tasks too.
• Playwright Documentation and Restful-booker, two of the stage resources.
• Ministry of Testing, the community the career stage points you to.
• Mutation Testing Bot That Grades AI-Written Tests on Pull Requests, a harder project once you finish.
• Related roadmaps: SQL and databases, DevOps and cloud and Your first tech job.

What you can do afterwards

Apply for QA engineer, test analyst and junior automation roles with a portfolio a hiring manager can open and understand in two minutes. From there the roadmap's own direction is towards SDET work: more code, deeper CI and test infrastructure. If you find you enjoy the pipelines more than the tests, the DevOps and cloud roadmap is a natural next step.

FAQ

How long does it take to learn QA and test automation? The roadmap estimates about 282 hours. That is roughly 26 weeks at 12 hours a week, or about 57 weeks at 5 hours a week.

Should I learn Playwright or Selenium? Playwright is the default here for modern web testing in TypeScript. Selenium is long established and common in Java teams. Choose the one your target job postings ask for; the roadmap's career stage asks you to tally 20 postings in your market for exactly this reason.

Do I need to know programming to become a QA engineer? For manual testing roles, less. For automation, yes: the roadmap gives programming 60 hours on its own before the automation stage.

Is the ISTQB certificate worth it? It opens some doors, but a repository a hiring manager can understand opens more. The roadmap asks you to read the syllabus and your local board's exam page, then write down your decision and the reasons for it.

Is QA still a good career in 2026? The roadmap treats it as a real specialism with a path into SDET. The testers it describes as hired fastest are the ones who ask the right questions about a vague story and write bug reports developers can reproduce in a minute.