PCB Testing Services

What Is PCB Testing?

PCB Testing is a process to ensure that a fabricated PCB or assembled PCBA meets all specified electrical and functional requirements. The criteria for testing change throughout the manufacturing process, from a fabricated PCB to an assembled PCBA to a powered product.

Bare-Board Testing vs. PCBA Testing

For example, when testing a bare PCB, the manufacturer must show that all conductive pathways intended to connect remain connected and that all other conductors remain isolated from each other. When testing an unpowered PCBA, additional evidence must show that the added components, soldered connections, circuit topology, and polarity of each connected component were manufactured correctly. When testing a powered PCBA, the evidence must include the proper operation of firmware, startup characteristics, power-supply rails, current consumption, interface and load characteristics, timing characteristics, and application response. Results from bare-board, unpowered PCBA, and powered PCBA testing are not interchangeable. A pass at one stage does not prove the conditions assigned to another.

What Does PCB Testing Verify?

PCB Testing Methods

Five services are used to verify the board but take different approaches based on access, fixture, and diagnostic methods: Bare-Board Electrical Testing defines what must be verified; Flying Probe, MDA, and ICT are ways of accomplishing that; FCT confirms operation when the item is under power.

Bare-Board Electrical Testing

Bare-Board Electrical Testing verifies the continuity and isolation of conductive paths, typically comparing the actual PCB against a netlist-derived continuity threshold and a predetermined isolation resistance at a specified voltage, not against an arbitrary pass/fail basis. Accordingly, the results of Bare-Board Electrical Testing provide information about the board revision, net status, applied test conditions, and, if necessary, where the fault occurred. If an assembly requires component verification or powered testing, it will be tested using Flying Probe, ICT, MDA, or FCT rather than through a standalone electrical test.

Flying Probe Testing

Flying Probe Testing uses a programmable test sequence and does not require a dedicated production fixture. It can test bare boards and unpowered PCBAs during prototyping, engineering revisions, lower-volume manufacturing, and when products are still in development because the program can be updated instead of requiring a new fixture.

The executable checks that can be performed with Flying Probe may include open-circuit tests, short-circuit tests, resistance tests, capacitance tests, inductance tests, diode tests, and selected component tests. Actual coverage depends on probe accessibility, circuit topology, parallel paths, component isolation, tester capability, and available design data. As circuits become more complex and there are more targets to test, recurring production cycle time may justify the use of a fixture to reduce test time.

In-Circuit Testing

ICT is performed with a fixture using controlled test programs to perform fast, repeatable tests on finished assemblies. Executable checks that can be performed by ICT include verifying open and short-circuit connections, testing parts for their correct values and polarity, and checking for production-related defects using the validated fixture.

When the board revision, BOM, test limits, production demand, and access to test points are stable enough to warrant fixture preparation, ICT is practical. Factors affecting the accessibility of test targets include probe reach, parallel paths, circuit isolation, and DFT access. ICT provides fixture-based electrical diagnostic capabilities, but it does not serve as a substitute for powered FCT.

MDA Testing

MDA uses analog signature analysis rather than digital vector testing; during this method, manufacturing defects are detected before full power-up by comparing a component's impedance response against that of a known-good component. Depending on accessible circuit nodes, circuit topology, and the selected platform, checks may include component values, polarity, opens, shorts, and connection conditions.

MDA can be used to provide component- or connection-level diagnosis without requiring the entire product to be powered. The limitations of MDA include target accessibility, parallel paths in the circuit, and the analog measurements available for the selected platform; this method does not provide evidence of powered operation or the behavior of active devices.

Functional Testing

FCT is conducted under the necessary conditions that allow the assembly to operate. FCT uses the necessary electrical protection, firmware, signals, interfaces, loads, input and output checks, and timing controls during execution. It can verify startup, rails, current, boot behavior, I/O, communication, timing, control logic, and application response.

FCT results depend directly on the specific fixture or setup, firmware, electrical load configuration, and limits that were in place when the test was executed.

How Does PCB Testing Scale with Production?

As demand stabilizes, production options shift from simple programming updates to ongoing production realities such as repeatability, cycle time, fixture cost, and unit cost. The sequence of testing types may change, but bare-board, unpowered, and powered test evidence can help determine different failure modes.

Prototype and Low-Volume Test Strategy

Prototype testing is generally performed without fixed production tooling, thereby allowing for a combination of Bare-Board Electrical Testing, Flying Probe Testing, and targeted FCT during the prototype design phase to accommodate PCB design changes.

Low-volume production testing may use a combination of Bare-Board Electrical Testing, Flying Probe Testing, MDA, and targeted FCT, based on the level of diagnostic coverage and output rate. After firmware, interfaces, loads, and acceptance limits have stabilized, functional coverage can expand.

What Changes in Volume Production?

ICT becomes practical for a PCB design when PCB revisions, BOM, DFT accessibility, limits, and measurement targets have become stable enough for fixture validation. MDA testing can continue where its coverage and cycle time fit the product, while FCT remains necessary to confirm powered operation.

Transition from Flying Probe to ICT

The transition from Flying Probe Testing to ICT will occur when stable product demand, test-point accessibility, and cycle-time savings justify the cost of fixture creation.

Correlation compares shared targets under equivalent conditions rather than assuming both methods produce the same evidence. Differences in probe paths, isolation methods, sequencing, instrument ranges, and limits must be resolved before ICT becomes the primary method for recurring production testing. Flying Probe Testing will remain appropriate for design revisions and diagnostic purposes during low-volume production.

The transition record retains PCB revisions, fixture identity, fixture validation status, ICT program, correlation of shared targets, resolution of differences between results, and the format of recurring results.

PCB Testing Process

Bare-Board Electrical Testing

Continuity and isolation are verified before the addition of electronic components to eliminate diagnostic ambiguity from components added to the assembly. Therefore, any defective bare board will be identified and dispositioned before assembly so that the fabrication defect does not consume electronic components or downstream testing capacity. The results retain the applicable condition, net-level status, and fault location when required.

The corrected or replacement bare board will undergo the same test definition.

Unpowered PCBA Testing

The assembly is tested in the unpowered state before full product operation using Flying Probe, ICT, or MDA according to the target defect and production stage. Executable checks may find opens, shorts, component values, polarity, and connection faults before full product power is applied to the assembly. The output is a net-level or component-level diagnostic result, not evidence of complete product performance.

Controlled Power-Up

The Controlled Power-Up step applies the source and protection limits established and recorded before full product functionality is applied. During this step, the station monitors the startup current, rails, and response of the assembly. If an abnormal condition exists during this step, the test will stop and will not apply full loads or interface activity to an unsafe condition. The Controlled Power-Up step produces a safe-power decision and records startup measurements.

Functional Verification

The FCT step uses the firmware, signals, interfaces, and loads required to exercise and verify product functionality. During the FCT step, startup, communication, I/O, timing, and load response will be compared with the acceptance limits established for the product. The output of the FCT step will remain linked to the operating configuration used during testing.

Failure Disposition and Retest

A repair does not close a failure. Engineering will retain the original result, failed condition, available diagnosis, corrective action, and affected sequence and will repeat that sequence using the same execution condition under which the failed condition was produced. The final status of the board—accepted, rejected, or quarantined—will be recorded with the initial failure, not in place of it.

Applications

Automotive Control Modules

Automotive control modules require controlled power sequencing, communication checks, connector load evaluation, and traceable hardware and software configurations. Bare-Board Electrical Testing indicates conductor integrity; Flying Probe, ICT, or MDA verifies accessible assembly defects; FCT verifies startup, network response, and driver behavior of the controller. Static test results may pass, while CAN or LIN wake-up, brownout recovery, and high-side or low-side fault conditions are revealed only after a load is applied to the connector. Gateway timing mismatch issues may only appear when all modules in a multi-ECU environment are tested together. Records must link the hardware revision and software variant to the load condition and response results.

Medical Monitoring and Control Electronics

Medical monitoring and control electronics must provide explicit coverage for low-level signals, sensor paths, alarm conditions, firmware-controlled functions, and interfaces. Unpowered methods are used to identify assembly and component defects before power-up. Once power is applied, FCT requires a simulator or precision source for offset, gain, threshold, and alarm-behavior testing related to the firmware and calibration state. The hardest failure to find is a board that boots normally and passes a single-point signal test but misreads or delays an alarm only at a clinically realistic input near the threshold.

Industrial PLC and Motor-Control Boards

Boards in an industrial environment use many I/O channels, field power, relays, drivers, and communication interfaces. Flying Probe, ICT, or MDA can be used to check for open circuits, short circuits, and component faults at accessible nodes before powering up the assembly. FCT applies representative field stimuli to 24V digital channels and 0-10V or 4-20mA analog channels, with relay and driver loads. These stimuli are recorded along with the channel number and response to distinguish a wiring fault from a firmware error. A channel may pass all tests when isolated from other channels but may fail once a relay load switches on an adjacent circuit; this coupling may only appear during simultaneous rather than sequential load testing.

Robotics and Motion-Control Electronics

Boards used for electric motors, robotics, and motion control can be affected by how electrical power is delivered from the external source to the motor; feedback timing for the position of the robot or motor; how the controller communicates with the driver; interlocks that prevent interference between motors, robots, or operators; and the timing between commands and responses. Testing the assembly without power applied will help identify assembly issues before power-up. FCT must include encoder or feedback simulation of the position of the motor or robot, interlock states, controlled drive loads, and checks of the timing of each command-response cycle. An assembly can pass electrical tests for all applied voltages; however, it may still encounter phase, direction, or latency failures when commanded to produce motion. The same is true for multi-axis designs; one axis can pass testing in isolation, but when the axes work together, a timing error may appear only when they move together.

Telecom Modules

Modules used for telecommunications require stable power, stable clocks, reset signals, digital interfaces, firmware configuration, and an appropriate response when the module receives commands. Bare-Board Electrical Testing verifies the conductor network of the board; Flying Probe, ICT, or MDA is used to verify accessible assembly conditions. FCT should isolate power faults, clock faults, firmware faults, link-training faults, and configuration failures. A telecommunications module can complete static link tests but experience signal-integrity or data-error-rate problems when running actual traffic; therefore, throughput tests are meaningful only when the interface and traffic patterns are defined at the time of testing.

IoT Gateways and Device Controllers

IoT gateways can include multiple firmware variants, sensors, low-power states, external interfaces, communication modules, and communication protocols. Testing the modules without power can provide information about component and assembly integrity before power-up. Following the unpowered test, event logging should be used to confirm boot from a cold start; sensor stimulus; interface response to external commands; reduced current draw in sleep mode; and the ability to wake on command without losing or improperly processing commands while an OTA firmware update window is pending. This timing relationship will not be revealed when FCT uses only a single power-on state.

Battery Management and Power-Conversion Boards

Power-conversion and battery-management boards require controlled starting conditions due to the interdependencies of sensing, switching, current paths, and protection logic under load conditions. Performing Bare-Board Electrical Testing establishes the integrity of the conductor paths, while unpowered PCBA testing allows for testing of accessible components and connections. FCT could require simulating cell voltage, calibrating current sensors, providing precharge or gate-drive sequencing, and confirming multiple protection thresholds. Applying full power before completing sensing or protection testing exposes the prototype to the greatest risk. A cell-balancing algorithm that successfully runs at mid-state of charge may leave blind spots at or near a fully charged cell or a near-empty cell state during balancing—those areas exhibit the least-tested balancing activity.

Aerospace and High-Reliability Control Electronics

Aerospace and High-Reliability Control Electronics require controlled configuration, auditable testing, and failure closure across electrical, unpowered, controlled power-up, and functional requirements assigned to specific requirements; they cannot simply group requirements under generic pass claims. Product-specific risks include watchdog operation, power-on self-test functionality, the availability and checking of redundant channels, and recovery from reset states. A redundant channel may switch over cleanly in a static test, but the redundant channel may still show a transient voltage drop during an actual failover—this transient condition can only be found by switching over a powered, loaded prototype and cannot be found using a logic-level test.

Test Reports and Deliverables

SUGA provides the deliverables in accordance with the agreed coverage statement and provides separate documentation for bare-board results, unpowered diagnostics, powered FCT results, and linked failure and retest records. Each deliverable is based on the particular board state and test method so that a pass status does not imply coverage for all possible targets, but only for those that were executed during testing.

Traceable Test Records