Quality Assurance
QA
- In Turkish
- Kalite Güvencesi
- Pronunciation
- KWOL-uh-tee uh-SHOOR-unss
In short
Quality assurance (QA) is the set of practices that ensure software meets its requirements and works reliably, aiming to prevent defects, not just find them.
What is quality assurance in software?
Testing checks whether a product works; quality assurance asks how the team builds products so that they work. QA covers the whole process: writing testable requirements, reviewing designs and code, agreeing on a definition of done, automating tests, checking releases and learning from bugs that reach users. In many companies QA is also the name of a role, the QA engineer, who plans and runs tests and champions quality.
A useful distinction is between assurance and control. Quality control finds defects in a finished piece of work, for example by testing a release candidate. Quality assurance improves the process that produces it, so fewer defects are created in the first place. Both are needed, and modern teams blend them into their everyday work instead of treating them as a final phase.
This blending is often called shifting left: involving testers early, writing automated tests alongside the code, running them on every commit in CI, and adding monitoring and feature flags so problems in production are noticed and contained quickly. Exploratory testing by people still matters, because humans spot confusing behavior that scripted checks miss.
A common misconception is that quality is the QA team's job. When developers hand code over to a separate team to be checked, bugs are found late and fixing them is expensive. Quality is shared: developers own tests for their code, product managers own clear requirements, and QA specialists bring testing expertise and strategy to the whole team.
Key takeaways
- QA is the set of practices that keeps software meeting its requirements.
- It aims to prevent defects, not only to find them.
- Quality control checks the product; quality assurance improves the process.
- Shift left: test early, automate in CI and monitor production.
- Quality is shared by the whole team, not just a QA department.
Example
// QA checks the product the way a customer uses it: here, buying a book, end to end
test("a customer can buy a book", async ({ page }) => {
await page.goto("/books/clean-code");
await page.getByRole("button", { name: "Add to cart" }).click();
await page.getByRole("link", { name: "Checkout" }).click();
await page.getByLabel("Card number").fill("4242 4242 4242 4242");
await page.getByRole("button", { name: "Pay" }).click();
await expect(page.getByText("Thank you for your order")).toBeVisible();
});Readers ask
What is the difference between QA and testing?
Testing is one activity: checking whether software behaves as expected. QA is broader and covers the whole process that leads to quality, including requirements, reviews, standards, automation and continuous improvement.
What does a QA engineer do?
Plans test strategies, writes and runs manual and automated tests, reports and tracks bugs, reviews requirements for testability and helps the team build quality into the development process.
What is the difference between QA and QC?
Quality control (QC) inspects the output to find defects. Quality assurance (QA) works on the process to stop defects from being made. QC is about the product; QA is about the way it is built.
See also
- Test AutomationTesting & Quality, p. 28Test automation is using code to run tests and check their results, so the same checks repeat quickly and consistently on every change instead of by hand.
- Test CaseTesting & Quality, p. 29A test case is a check of one specific behavior: starting conditions, input or steps, and the expected result that shows if the software behaves correctly.
- Regression TestingTesting & Quality, p. 22Regression testing is the practice of re-running existing tests after a code change to make sure that features which used to work have not broken.
- Exploratory TestingTesting & Quality, p. 9Exploratory testing is a hands-on approach in which a tester learns about the software, designs tests, and runs them at once, guided by what they discover.
- Code ReviewVersion Control, p. 4A code review is the practice of having other developers check code changes before they are merged, to catch bugs, improve quality, and share knowledge.
- Definition of DoneTeams & Process, p. 7The Definition of Done is a shared checklist of quality standards that every piece of work must meet before a team can consider it complete.
Free · once a week
Software and AI, explained once a week
The week's software and AI news with every term explained, plus a term to learn and a quick quiz. A two-minute read.
See this week's issueAbout this page
Page history
Added a code example: an automated QA check of the checkout.
Changes that altered what this page says. Typo fixes are not listed.
Spotted a mistake or something missing on this page?Suggest an edit
How pages are made