Quality Assurance vs Quality Control vs Testing.

Process confidence, result evidence and a specific evaluation

These activities reinforce one another. Assurance can improve the testing process; testing supplies evidence; control interprets evidence and decides whether the output conforms. Do not choose a label only because the word “quality” appears.

Quality assurance: prevent and improve

Quality assurance gives stakeholders confidence that appropriate processes and practices can consistently produce conforming results. It looks at the system of work rather than waiting for a finished deliverable to expose defects.

• Review whether the quality approach is appropriate for the product, risk and regulatory context.
• Use process audits, retrospectives, peer reviews and root-cause analysis to identify improvement opportunities.
• Confirm that standards, responsibilities, measurement methods and escalation paths are understood.
• Improve prevention through automation, training, reusable checklists, clearer entry criteria or safer engineering practices.
• Share learning across teams so recurring causes are removed rather than repeatedly inspected out.

Exam mindset: assurance is not a separate department that owns all quality. The team remains responsible for building quality into work; specialists and audits support that responsibility.

Quality control: evaluate actual results

Quality control examines a deliverable, service result or process output and compares the evidence with requirements, acceptance criteria, the Definition of Done, quality metrics or other tolerances. The work happens throughout delivery, not only before handover.

Control data should lead to action. If a result misses a threshold, make the nonconformance visible, protect users, determine impact and correct the work. A repeated pattern also signals a process problem that assurance and improvement activities should address.

Testing: one family of quality-control techniques

A test defines an objective, preconditions, inputs, execution steps and an expected result. The team compares actual behavior with that expected result and records evidence. Testing can target function, integration, security, usability, accessibility, recovery, load or another quality characteristic.

1. Trace the test objective to a requirement, risk, acceptance criterion or quality metric.
2. Define the environment and data so results are repeatable and meaningful.
3. Include positive, negative and boundary conditions based on impact and uncertainty.
4. Record actual results and defects without changing the expected answer after execution.
5. Retest corrections and relevant regression paths before declaring conformance.

Testing alone cannot prove the process is capable, the customer need is correct or every possible defect is absent. It provides bounded evidence for a decision.

Verification vs validation: right specification vs right outcome

Both matter. A team can build a conforming result that solves the wrong problem, or a desirable concept that fails mandatory requirements. In situational questions, first determine whether the issue is conformance, intended value or both.

Worked scenario: healthcare appointment release

A team prepares an online appointment service for release. Functional tests pass, but a late audit finds that teams use different methods to anonymize test data.

1. The passed functional tests are testing evidence, but they do not cover every quality or compliance risk.
2. The audit finding concerns the process and control environment, so the project manager facilitates an assurance and compliance review rather than ignoring it because the feature works.
3. The team contains exposure, confirms applicable privacy requirements and checks whether any real data was used.
4. It standardizes anonymization, assigns ownership, updates the quality approach and automates a guardrail.
5. Quality control then evaluates affected builds and evidence against the corrected criteria.
6. Relevant tests are rerun; only conforming work proceeds through the agreed release decision.

The strongest answer protects users first, uses evidence, involves the right specialists and improves the process so the failure is less likely to recur.

What to do when quality evidence fails

1. Stop unsafe progression: do not trade a material quality, security or regulatory failure for schedule appearance.
2. Confirm the criterion and evidence: distinguish an actual nonconformance from a faulty measurement or unclear requirement.
3. Assess impact: identify affected users, deliverables, integrations and releases.
4. Find root cause collaboratively: look beyond the person who detected or introduced the visible defect.
5. Correct and verify: repair the result, retest it and check regression or downstream effects.
6. Improve prevention: update the process, automation, training or quality standard when the cause is systemic.
7. Communicate transparently: update defect, risk, issue and stakeholder information through the chosen delivery approach.

PMP practice checks with explanations

Common PMP exam mistakes

• Calling every test “quality assurance.”
• Inspecting only at the end instead of building quality into delivery.
• Assuming a passed test proves every quality characteristic.
• Accepting a defect to protect the schedule without impact analysis and authorization.
• Blaming the tester or developer instead of examining the system and root cause.
• Confusing verification of specifications with validation of intended value.
• Collecting quality data without thresholds or decisions tied to it.
• Making the project manager or quality specialist solely responsible for quality.

Frequently asked questions

Official PMI references

Use the July 2026 PMP Examination Content Outline for current exam scope. PMI's learning library also explains quality planning, assurance, control and improvement, practical quality-management tools and continuous inspection, measurement and testing. Adapt practices to the product, delivery approach, regulation and organizational context; ITCertPath does not reproduce confidential exam questions.