←  All terms
Q
QA & Deployment

Quality Assurance

Quality assurance uses planned checks and standards to prevent defects and produce reliable digital outcomes.

Quality assurance uses planned checks and standards to prevent defects and produce reliable digital outcomes. Automated checks speed up validation but do not replace focused manual testing of critical user journeys. The concept is closely related to Cross-Browser Testing and Regression Test.

Read more

Cross-Browser Testing

Regression Test

Design QA

Accessibility Audit

FAQ

Quality Assurance

How much automation makes sense in quality assurance?
Recurring, clearly verifiable items should be automated, such as links, regression cases, Lighthouse scores, and code style. Usability, content, and critical user journeys stay manual, because people notice anomalies that no rule covers. Together the two provide more assurance than either approach alone.
When in a project should quality assurance begin?
From the start, not just before launch. Requirements, designs, and concepts can be checked early for contradictions and accessibility; corrections are cheapest there. A final-stage check alone finds defects that can then often only be fixed under deadline pressure or with compromises.
What distinguishes quality assurance from testing?
Testing is an activity: properties of the software are checked. Quality assurance additionally covers processes, standards, and checklists meant to prevent defects in the first place. Testing finds defects; quality assurance prevents some of them, for example through code reviews, a definition of done, and clear approvals.
Which checks belong to quality assurance for a website?
They include functional tests, cross-browser and device checks, an accessibility audit, performance measurement, SEO checks, and review of content, forms, and redirects. The scope follows risk. Critical user journeys such as contact or purchase are always checked, less important pages by sampling.