New: Practical guidance for AI-assisted quality engineering
AskAQA · Cornerstone Page 08

What If a Vendor Says Testing Is Complete?

A practical enterprise scenario for assessing vendor testing claims using strategy, coverage, traceability, evidence, defects, exit criteria, and independent review.

10 min readPractical QA guidance built around situations, evidence, risk, decisions, and next actions.

The situation

A vendor reports that testing is complete, but provides a high-level status summary and limited evidence.

What “complete” should mean

  • Agreed scope validated
  • Traceability exists
  • Critical scenarios executed
  • Defects assessed
  • Regression addressed
  • Evidence retained
  • Exit criteria met
  • Known limitations documented

What to request

AreaEvidence
StrategyScope, test types, ownership, environments, exit criteria
CoverageRequirements-to-test mapping
ExecutionRepresentative results and evidence
DefectsOpen/closed defects and severity decisions
ReleaseResidual risk and acceptance

AskAQA recommendation

Recommendation
Treat vendor completion as an input, not automatically as customer acceptance. Review representative evidence independently, especially for high-risk integrations, data migration, regression, and operational readiness.

Have a real QA situation?

Describe the context, risk, constraints, and decision you need to make. AskAQA will help structure the problem and identify practical next actions.

Ask a QA Question

AskAQA AI assistant

Ask a QA

Ask me a software quality question, or ask how AskaQA knowledge areas can help you think through a QA decision.

Do not include passwords, confidential information, or personal data in your question.