What is software quality assurance?

QA vs testing vs quality engineering

Testing finds defects. Quality assurance is the system around testing: the process, strategy, automation, and reporting that decide what gets tested, how deeply, and how the results turn into decisions. Quality engineering is the discipline of building that system with engineering rigor — maintainable, observable, and CI/CD-native.

The layers of quality assurance

A working quality assurance system has four layers:

• Process — scope, environments, risks, and exit criteria agreed before testing starts.
• Test strategy — what to test, at what depth, and how often, based on risk rather than habit.
• Automation — repeatable suites for the checks that would otherwise consume the team's capacity.
• Reporting — severity-classified findings with evidence, area-by-area status, and an explicit release recommendation.

How QA fits into the release cycle

Quality assurance is not a phase at the end — it is a set of gates throughout. Smoke suites run on every change, regression runs before every release, and each release starts from a known baseline. The question QA answers is not "are there bugs?" but "is this ready?" — with evidence.

What good QA looks like

Good QA is honest. If the answer is hold, the report says hold — with the reasoning and evidence behind it. The published sample assessment on this site shows the deliverable format: reproducible findings, severity classification, and a clear release recommendation.

Where quality assurance is heading

AI is changing the economics of QA: requirements analyzed into structured test cases, OpenAPI specifications turned into pytest suites, and CI failures triaged into root causes with suggested fixes. The CypherPilot platform is a working, open-source example — with human verification retained at every step.