What is QA testing? It's the work of checking that software does what it's supposed to do before real users find out it doesn't. If you've heard the term in a job ad, a sprint meeting or a career video and weren't sure what it covers, this guide explains it in plain language, with no coding required.
You'll learn what QA means in software, how QA differs from QC and testing, which QA activities happen at each stage of a project, the main types of QA testing, and a real example you can follow: testing a login page step by step. At the end, you can check your own readiness with a free 20-question test.
What Is QA Testing?
QA testing is the process of checking software against its requirements to find defects before release. QA stands for quality assurance. Testers review requirements, design test cases, run them manually or with automation tools, report bugs, and confirm fixes, so the product works correctly, securely and reliably for users.
In day-to-day conversation, people use "QA testing" and "software testing" almost interchangeably. Strictly speaking, QA is the wider umbrella: it includes testing, but also the processes, reviews and standards that stop bugs from being written in the first place. We'll separate those terms properly in a moment.
QA Meaning in Software
In software, QA means quality assurance: a set of planned activities that give a team confidence the product meets its requirements and its users' expectations. It's not the same as "Q&A" (questions and answers), even though the two are often confused in search results and chat messages.
When someone says "send it to QA" or "it failed QA", they mean the build is being checked, or was checked and found to have problems, by the people responsible for quality. Those people are usually called QA testers or QA engineers.
So, what is QA in software testing specifically? It's the mindset and process that sits around the testing itself: agreeing what "done" means, writing acceptance criteria, reviewing designs for gaps, choosing what to test and how deeply, and tracking quality over time. Testing is the hands-on part where you actually run the checks.
QA vs QC vs Testing
These three terms overlap, and job titles don't always use them precisely. Here's the cleanest way to tell them apart:
| Quality Assurance (QA) | Quality Control (QC) | Testing | |
|---|---|---|---|
| Focus | The process | The product | Specific features and behaviour |
| Goal | Prevent defects | Find defects in what was built | Execute checks and report results |
| When | Throughout the whole project | After something is built | During development and before release |
| Examples | Requirement reviews, test strategy, coding standards | Inspections, release sign-off, audits | Running test cases, exploratory sessions, automated suites |
| Question it answers | "Is our process set up to prevent defects?" | "Does the finished product meet its requirements?" | "Does this feature behave as expected right now?" |
In practice, most software teams roll all three into one "QA" role. A QA tester reviews requirements (QA), runs test cases (testing) and signs off a release (QC), often in the same week.
QA Across the SDLC and STLC
The software development life cycle (SDLC) is the journey from idea to release. The software testing life cycle (STLC) is the testing work that runs alongside it. Good QA starts early, an approach called shift-left testing, because a gap spotted in a requirement costs far less to fix than a bug found by a customer.
| SDLC stage | What QA does |
|---|---|
| Requirements | Review user stories, ask "what happens if…?", agree acceptance criteria |
| Design | Spot untestable or missing flows, plan the test strategy and test data |
| Development | Write test cases, prepare environments, test early builds and APIs |
| Testing | Run functional, regression and exploratory tests; log and retest bugs |
| Release | Run smoke tests, confirm critical bugs are fixed, give sign-off |
| Maintenance | Investigate production issues, add regression tests so bugs don't return |
The STLC breaks the testing part into its own steps: requirement analysis, test planning, test case design, environment setup, test execution and test closure. Ready-made formats for each step are in our software testing templates.
Types of QA Testing
QA testing splits into two big families, plus two ways of running the tests.
Functional testing
Checks what the software does. Does the login work? Does the cart total add up? It is done at different test levels (unit, integration, system and user acceptance testing, or UAT) and repeated after changes through smoke, sanity and regression checks.
Non-functional testing
Checks how well it does it: performance under load, security, usability, accessibility and compatibility across browsers and devices.
Manual vs automated testing
| Manual testing | Automated testing | |
|---|---|---|
| Who runs it | A person, step by step | A script or tool |
| Best for | New features, exploratory and usability testing | Repeated regression checks, many browsers, CI pipelines |
| Skills needed | Test design, attention to detail, clear bug reports | All of those, plus a programming language and a tool |
| Where beginners start | Yes, the usual entry point | The next step after the basics |
For the full list with examples of each, read types of software testing.
Not sure where you stand? Take the free QA tester test (20 questions, instant score) and get a recommendation for what to learn next.
QA Testing Example: A Login Page
The fastest way to understand QA testing is to see it on something familiar. Imagine a login page with an email field, a password field and a "Log in" button. The requirement says: "Registered users can log in with their email and password. Wrong details show an error message. The account locks after repeated failed attempts."
A QA tester turns that requirement into test cases like these:
| ID | Test case | Steps | Expected result |
|---|---|---|---|
| TC-01 | Valid login | Enter a registered email and correct password, click Log in | User lands on the dashboard |
| TC-02 | Wrong password | Enter a registered email and a wrong password | Error message shown; user stays on login page |
| TC-03 | Unregistered email | Enter an email that has no account | Same generic error (no hint that the email doesn't exist) |
| TC-04 | Empty fields | Click Log in with both fields empty | Validation messages for both fields |
| TC-05 | Invalid email format | Enter "user@" as the email | Format validation message |
| TC-06 | Account lockout | Enter a wrong password repeatedly | Account locks after the agreed limit; message explains next steps |
| TC-07 | Password is masked | Type in the password field | Characters are hidden |
| TC-08 | Keyboard only | Tab through fields and press Enter | User can log in without a mouse |
Notice that TC-06 exposes a gap: the requirement says "repeated" attempts but doesn't say how many. Asking that question during requirement review, before any code exists, is QA in action. If TC-02 failed, the tester would write a bug report with the steps, expected result, actual result, environment and a screenshot.
Want to practise this on a real site? Our guide to how to test a web application walks through a full checklist.
Who Does QA Testing?
On most teams, QA testing is owned by a QA tester (also called a software tester or QA analyst). As teams grow you'll also see QA engineers, automation engineers and SDETs (software development engineers in test), who write code to automate tests. Developers test their own code too, usually with unit tests, and product owners join in during user acceptance testing.
Curious what the job looks like day to day? Read what is a QA tester for responsibilities, skills and how to become one.
QA Testing Tools
| Category | What it's for | Common examples |
|---|---|---|
| Issue tracking | Logging bugs and tracking user stories | Jira, Azure DevOps, Linear |
| Test management | Storing test cases, test runs and results | TestRail, Zephyr, Xray, qTest |
| API testing | Checking back-end endpoints | Postman, Playwright API testing |
| Browser automation | Running UI tests automatically | Playwright, Selenium, Cypress |
| Browser dev tools | Inspecting pages, network calls and console errors | Chrome DevTools, Firefox DevTools |
Beginners usually learn Jira and a test management tool first, then a browser automation tool. Playwright is a popular choice for that step because it's free, works across Chromium, Firefox and WebKit, and handles waiting automatically. See what is Playwright testing for a beginner overview.
How AI Is Changing QA Testing
AI hasn't replaced QA testing, but it has changed some of the work. Here's what's genuinely useful today:
- Drafting test cases. Paste a user story into Claude or ChatGPT and ask for positive, negative and edge cases. You get a first draft quickly, then use your judgement to remove duplicates and add what it missed.
- Writing clearer bug reports. AI can tidy rough notes into structured steps, expected and actual results.
- Generating test data. Realistic names, addresses and boundary values for forms.
- Writing automation code. With the Playwright MCP Server, an AI assistant can open a real browser, explore a page and help write Playwright tests that you then review and run.
What AI can't do is decide what matters to your users, question a vague requirement, or take responsibility for a release decision. Its output still needs checking, and checking things carefully is exactly the skill QA testers are hired for. Testers who learn to use AI well tend to get more done, not less.
How to Start Learning QA Testing
- Learn the fundamentals: SDLC, STLC, test types and test design techniques.
- Practise writing test cases and bug reports on real websites.
- Learn Jira and how QA fits into Agile sprints.
- Add API testing basics.
- Move into automation with a tool like Playwright.
For a structured order, follow the software testing learning path, or start with the free software testing tutorial. Comparing courses? See the software testing course path.
Frequently Asked Questions
What is QA testing in simple words?
QA testing is checking that software works the way it should before people use it. A QA tester reads what the software is supposed to do, tries it out in planned and unplanned ways, and reports anything that is wrong so developers can fix it.
What does QA mean in software?
QA means quality assurance. In software it covers all the planned activities that help a team deliver a working product, including reviewing requirements, planning tests, running tests and reporting defects. It is different from Q&A, which means questions and answers.
What is the difference between QA and QC?
Quality assurance (QA) focuses on the process and aims to prevent defects, for example by reviewing requirements early. Quality control (QC) focuses on the finished product and aims to find defects in it. In most software teams, one QA role does both.
Is QA testing manual or automated?
Both. Manual testing is when a person runs the checks step by step, and it is the usual starting point for beginners. Automated testing uses tools such as Playwright or Selenium to run repeated checks with code. Most teams use a mix of the two.
Do you need coding skills for QA testing?
Not to start. Manual QA testing needs test design, attention to detail and clear communication. Coding becomes important when you move into test automation, where JavaScript, TypeScript, Python or Java are commonly used.
Will AI replace QA testing?
AI is changing QA work rather than replacing it. Tools like Claude and ChatGPT can draft test cases and test data, and the Playwright MCP Server helps write automated tests. People are still needed to judge what to test, check AI output and decide whether a release is ready.
Asim Noaman
Senior QA Automation Engineer & AI Testing Specialist
With years of hands-on experience building test automation frameworks for production applications, Asim specializes in combining traditional QA methodologies with cutting-edge AI tools. He has helped teams adopt Playwright and AI-driven testing workflows to ship faster with fewer bugs.
Starting a QA Career?
Learn QA Testing the Way Teams Actually Do It
Manual Testing & QA with AI takes you from "what is QA?" to writing real test cases and bug reports, with ChatGPT and Claude AI helping you work faster. It's built for beginners and career switchers aiming for a first QA job.
- QA fundamentals: SDLC, STLC, test types and test design
- Write test cases and bug reports for real applications
- Use ChatGPT and Claude AI to draft and review testing work
- 4.5★ on Udemy, 660+ students, 30-day money-back guarantee
Prefer AI-driven, no-code testing? AI Software Testing for Beginners · Ready for automation? Playwright + Claude AI