PCB Test Plan Checklist | PCBLaunch

Start before power is applied

Document polarity, expected resistance or shorts checks, supply limits, connector orientation, and the safe order for first power-up.

Separate manufacturing checks from product behavior

Continuity, opens, shorts, solder quality, programmed-device access, and functional behavior answer different questions. A single pass label should not hide which checks were actually performed.

Make the setup repeatable

Name the firmware, fixture, instruments, cables, loads, environmental condition, and test sequence needed to reproduce the observation.

Record exceptions

If a check cannot be completed, record why, what evidence is missing, and whether the limitation blocks release or only narrows confidence.

Working checklist

Board revision
Safe power limits
Test setup
Firmware version
Input condition
Expected result
Recorded observation
Pass or decision rule
Exception handling

Use as preparation, not as a universal specification

The final technical, sourcing, testing, timing, and handover requirements depend on the submitted project and responsible approvals.

Prepared for PCBLaunch project reviews. Reviewed by Li Can. Updated 2026-10-13.

Test plan guide

A test plan turns a prototype into usable evidence.

The goal is not to create paperwork for its own sake. It is to make the build condition, expected behavior, recorded result, and decision rule clear enough to repeat.

Before power

Confirm revision, setup, input condition, safety boundary, and what must be true before the board is energized.

During the check

Separate manufacturing defects from product behavior and record the actual action, expected result, and observed output.

After the check

Keep exceptions, rework, limits, and approval decisions connected to the revision that was tested.

Why the test plan matters

A repeatable test protects the decision after the prototype leaves the bench.

When the setup and expected result are explicit, a failure can be investigated instead of argued about. That is what lets the customer approve a revision with confidence.

Record the condition, not just pass or fail

Input state, action, observed output, limits, and exceptions make the result meaningful to the next build.

A test is a decision tool

Every useful test names the setup, the behavior and the evidence that closes it.

A test plan turns “it seems to work” into a repeatable way to decide whether the board can move to the next gate.

Setup

State the board revision, firmware or configuration, fixture, instruments, power and environmental conditions.

Stimulus

Describe the input, sequence, load or operator action that should produce the expected behavior.

Expected result

Use observable outputs and limits rather than a general statement that the board is good.

Disposition

Define what happens after pass, fail, rework, retest or an unexplained result.

Test-plan questions

What makes a test useful on the next batch?

Does functional testing replace inspection?

No. Visual, assembly and process checks catch different risks. The test plan should state which boundary each check covers.

Can a customer define the test without instruments?

Yes, if the expected behavior and observable evidence are clear. The required setup can then be scoped honestly.

What if the first test reveals a design issue?

Record the condition and decision. A test finding may trigger rework, redesign or a new acceptance boundary rather than a silent pass.

PCB Prototype Test Plan Checklist