FVT Testing and FCT: Meaning, Coverage and Test Planning

In PCB assembly, FVT testing can refer to functional verification of a populated board. FCT commonly means functional circuit test. Confirm how each term is used in your project, then define the functions, operating conditions and pass/fail limits in writing; the acronym alone does not define test coverage.

What does FVT mean, and how does it relate to FCT?

In this board-assembly context, both labels may describe powering a board and checking documented behavior. FCT is commonly expanded as functional circuit test or functional test. FVT may refer to a functional verification test, a tester or a stage in a particular company's workflow. Confirm the full term and acceptance procedure with the project team rather than assuming a universal distinction.

That matters commercially. If a quote or a test plan says only "FVT," the scope is undefined: two suppliers can deliver very different testing under the same three letters. FVT and FCT are not mutually exclusive standard methods, and neither term prescribes a sequence. A project may run one, the other, or both, and separately named tests can carry different scopes: document each stage's functions, conditions and pass/fail criteria rather than reading an order or sequence into the acronym.

Define the test scope, not the acronym

A functional test exercises documented board functions under defined conditions; it does not guarantee that every possible defect will be found. Before equipment is chosen, write the scope down:

• Functions to exercise — power-up behavior, key inputs and outputs, displays, communication interfaces, stored data.
• Conditions — supply voltages, loads, firmware or software version, warm-up and ambient assumptions.
• Pass/fail criteria — the measured or observed result that separates pass from fail for each function.
• Record format — what is logged per board: serial number, result, date, fixture ID, software version.
• Disposition — what happens to a failing board: retest, debug, rework loop or scrap.

With the scope written down, the acronym on the purchase order becomes a label rather than a promise.

Fixture options: system hookup, wired fixture, interface PCB

Test equipment and method vary by product. Three hookup approaches are worth comparing, and they differ in effort, repeatability and signal fidelity — not in what "counts" as FVT or FCT.

Fixture type is not a coverage claim. A more elaborate fixture is not automatically a more thorough test — coverage comes from the written scope, not from the hardware. Note too that when a fixture or extension cable replaces an original connector, the interconnect itself changes, and signal and return-path behavior can shift. Our design guide on layout and return paths covers the board-side principles this affects.

Coverage and limits vs visual inspection and ICT

Functional testing is one layer of a test strategy, not the whole of it. Visual inspection catches assembly defects — missing, misaligned or poorly soldered parts — that a functional test may never reveal if the board still powers up. In-circuit test (ICT) commonly measures components and solder joints with the board unpowered, and depending on the equipment and test program it may also include powered checks; coverage is not universal across ICT setups. What it adds is detection of manufacturing defects — shorts, opens, wrong or out-of-tolerance parts — that functional testing can miss or that appear only intermittently.

ICT and functional testing therefore complement each other rather than compete: they address different failure modes. A functional test cannot certify complete defect coverage, and a "100% tested" statement says nothing about which defects the test can actually see. State the scope and the checks used, and let the records demonstrate the rest.

Test handoff and pass/fail record checklist

Whether testing runs in-house or at an assembly supplier, settle the following before the first board is powered:

• Golden sample boards are identified, protected and version-controlled and used as a reference aid alongside — not as a substitute for — defined, measurable acceptance limits; repeated plugging damages connectors and cables, so plan extension interfaces where they are needed.
• Every board is traceable to an identifier — a per-unit serial number or a batch-level identifier, as agreed for the project — plus build version and test record.
• Pass/fail results are logged per function, not just as an overall verdict.
• Failures route to a defined disposition — retest, debug or rework — and the post-rework result is recorded.
• The fixture ID and the firmware or software version are captured with each record.

RFQ inputs and next step

Quoting a functional test takes more than a bare assembly quote: fabrication data, the BOM, expected volumes and the preferred fixture approach, plus the test-specific inputs — firmware or software version, I/O definitions, loads and stimulation needs, pass/fail limits, fixture requirements and the records you want kept. If those are not ready yet, the first contact can simply describe the product and the files you already have, and scope, records and acceptance criteria are confirmed in writing before production. The PCB assembly services page can be used to discuss assembly scope alongside those files.

Whatever the purchase order says — FVT, FCT, or both — the scope document is what actually gets tested.