PCBA Functional Testing: Write a Usable Test Plan

“Please test the board” does not define a repeatable acceptance procedure. A useful functional test plan tells the operator how to configure the assembly, what to measure and how to decide whether it passes. Agree the scope before quotation so tooling and execution can be evaluated.

Define the unit and setup

Identify the PCB revision, assembly variant and firmware version. List required cables, loads, fixtures, software and equipment. Describe the connection order and the approved supply settings, including protection limits established by the responsible engineer. Do not ask the operator to invent a power-up sequence from the schematic.

State whether testing occurs before or after enclosure assembly and whether programming forms part of the process. If a reference unit is supplied, give it an identifier and explain what it demonstrates. A reference unit is helpful context but does not replace written acceptance limits.

Make each step measurable

For every step, write the input condition, action, measurement point, allowed result and record required. Replace “LED works” with the expected indicator behavior under a defined input. Replace “output is normal” with a limit derived from the product specification.

An illustrative row might contain: “Apply the approved input condition; measure TP3 relative to TP0; compare with the engineering-approved range; record the measured value.” The actual voltage and limits must come from the product owner. This format avoids inventing a universal electrical criterion.

Specify failure handling

Explain when to stop testing, what evidence to save and who reviews a failure. Avoid repeated power cycles or unapproved rework that can obscure the original symptom. Identify any permitted retest and how it should be recorded separately from the first result.

• Match the procedure to accessible test points and connectors.
• Include firmware files and their version identifiers.
• Define pass limits and environmental assumptions.
• Specify required serial-number or batch traceability.
• Agree the report format and retention requirements.

Prove the procedure on a first article

Have someone other than the author execute the written steps using the intended setup. Record unclear instructions, inaccessible points and missing equipment, then revise the procedure. Confirm the agreed testing service and any fixture costs with DIYIPCB before the production build. Keep the accepted test revision tied to the assembly variant so later orders use the correct limits and firmware.