What is Conformance Testing?

Conformance testing (compliance testing) verifies that a product, system, or implementation adheres to a defined standard, specification, or regulation, confirming it follows the prescribed rules so it will interoperate and be accepted where that standard is required.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Conformance testing checks a system against an external rulebook rather than just its own requirements. The "rulebook" might be a technical standard (HTTP, USB, WCAG accessibility, HTML, OAuth), an industry specification (HL7/FHIR, ISO 20022, PCI DSS), or a regulation. The question is not only "does it work?" but "does it work the way the standard mandates?", because conforming is what makes systems interoperable and compliant.

It is often performed with standardized conformance test suites or certification programs provided by the standards body, which define the exact checks an implementation must pass. Passing can be a prerequisite for certification, market access, or integration into an ecosystem (for example, a payment terminal must pass certification, or an accessible site must meet WCAG criteria).

Conformance testing overlaps with but differs from functional testing: functional testing verifies the product meets its own requirements, while conformance testing verifies it meets an external standard, two things that can diverge (a product can function yet violate a standard, or conform yet not meet a user need). It also relates closely to interoperability testing, conforming to shared standards is often what enables systems to interoperate.

WHY IT MATTERS

Why interviewers ask about this.

Conformance testing matters for regulated, standards-based, and accessibility-focused roles. Distinguishing it from functional testing (external standard vs own requirements) and linking it to certification and interoperability shows you understand quality where compliance, not just behavior, is the bar.

EXAMPLE

Example scenario.

A web team runs conformance testing against WCAG 2.2 AA to certify accessibility. The site is functionally fine, but conformance checks reveal missing form labels and insufficient color contrast that violate the standard, defects that block compliance and must be fixed before the site can be declared conformant.

TIP

Interview tip.

Define conformance testing as verifying a product adheres to a defined standard, specification, or regulation (often via standardized conformance suites or certification). Contrast it with functional testing (meeting your own requirements) and connect it to interoperability and certification to show you grasp compliance-driven quality.

FAQ

Frequently asked questions.

What is the difference between conformance testing and functional testing?

Functional testing verifies a product meets its own requirements (does it do what we intended?). Conformance testing verifies it meets an external standard, specification, or regulation (does it follow the prescribed rules?). They can diverge: a product can work yet violate a standard, or conform yet not meet a user need.

Where is conformance testing required?

Wherever standards or regulations govern acceptance: accessibility (WCAG), web standards (HTML, HTTP), hardware (USB, Bluetooth), healthcare data (HL7/FHIR), payments (PCI DSS, ISO 20022), and many certification programs. Passing conformance tests is often a prerequisite for certification, market access, or ecosystem integration.