Apps & Software
What is Quality Assurance (QA)?
Also called QA, software quality testing, software testing.
Short definition
Quality assurance (QA) is the set of activities that ensure software meets the agreed requirements and quality standards, from writing test scenarios to testing every release before it reaches users.
How it works
The QA team reads the application requirements and then writes test scenarios: what the user does and what result should appear. Those scenarios are run manually, automatically, or both, in a staging environment. Findings are logged as bug reports with clear steps, fixed by developers, and then retested. Some automated tests run every time code changes through CI/CD. Regression testing ensures existing features keep working after new ones are added, something often missed when testing only happens at the end of a project.
QA versus UAT
QA is done by the build team to ensure the application works as designed and does not break existing functions. UAT is done by users on the company side to ensure the application truly fits the way they work. The two complement each other; UAT without QA usually turns into an exhausting bug hunt for users.
What to ask a vendor
Whether there is a separate QA stage, who does it, what gets tested, such as functionality, display across devices, performance, and basic security, and how bugs are reported and tracked. A proposal that does not mention testing at all deserves scrutiny, because fixing bugs after an application is in use costs far more than catching them early.
Related terms
Further reading
Resources
- NIST Glossary: quality assurance (csrc.nist.gov)