A software tester finds problems before users do. You read requirements, think about how things can break, run tests, write clear bug reports, and help decide when a product is ready to ship. Most testers start by testing by hand, then learn to automate with code (Selenium, Playwright, Cypress), test APIs (Postman), and query databases (SQL). No license is legally required. A bachelor's degree is common (about half of workers), but many people get hired with an associate's degree, a bootcamp-free self-study portfolio, or a career change. Employers look for proof: a portfolio on GitHub with tes
See the full roadmap free
Every stage from beginner to expert, with lessons, practice drills, projects, interview questions and free resources. Free with a Rolearch account.
Stage 1 of 4 · about 8 weeks
Understand the software lifecycle (SDLC, Agile, Scrum) and testing basics: test levels (unit, integration, system, acceptance), black-box techniques (equivalence partitioning, boundary value analysis, decision tables), and positive vs negative testing. Write clear test cases and bug reports (title, steps, expected vs actual, severity, environment). Practice on real sites like a free demo e-commerce app, and log bugs in a free Jira or GitHub Issues board. Learn basic SQL (SELECT, WHERE, JOIN) and basic browser DevTools.
SDLC, Agile, Scrum and test levels
Testers do not work alone. You test inside a process, and knowing where testing fits tells you when to ask questions, what to test, and who to talk to. Job postings mention Agile and Scrum almost every time.
Black-box test design and writing test cases
You cannot run every possible test. Design techniques let you pick a small number of tests that find the most bugs. Writing them clearly means anyone can repeat your work, which the job explicitly requires.
Bug reporting and tracking with GitHub Issues or Jira
Finding a bug is only half the job. A report that a developer can understand and reproduce in one read gets fixed fast. A vague one gets ignored and damages trust. Bug reports are also what hiring managers look at in a portfolio.
Browser DevTools and basic SQL for testers
DevTools let you see why a page misbehaves, so your bug reports include real evidence. SQL lets you confirm the data behind the screen is right, such as whether an order was really saved. Both are listed in nearly every entry-level QA posting.
Then 3 more stages (about 74 weeks in all) with lessons, drills, projects, 10 interview questions with strong answers and free resources.