ENGINEERING INSIGHTS

PCB • PCBA • Control Boards • Electronics Manufacturing
Practical knowledge from design and component sourcing to PCB assembly, testing and mass production.
click

AOI vs. FCT: What Each PCBA Test Can Verify

By RONGHE Engineering Team October 10th, 2026 35 views

AOI vs. FCT: What Each PCBA Test Can Verify

By David · RONGHE

AOI and functional testing answer different questions about a PCB assembly. Learn what each method can check, where its limits lie, and which test requirements to prepare before discussing your project with a manufacturing partner.

AOI and FCT comparison cards over a factory production-line photo, showing visible assembly inspection and defined functional checks.

A PCB assembly can pass an appearance inspection and still fail to perform a required function. It can also operate during a functional test while an assembly condition still needs investigation. For a useful PCBA test plan, distinguish automated optical inspection (AOI) from functional circuit testing (FCT), then define what each result is intended to demonstrate.

This guide explains the difference and provides a checklist for discussing inspection and testing with your manufacturing partner. The scope should be agreed for the individual project.

What Does AOI Check?

AOI examines the visible condition of an assembly using optical inspection. Depending on the equipment, program, component visibility, and acceptance criteria, it can help identify misplaced or missing components, orientation issues, and visible solder anomalies.

  • Missing or shifted components
  • Polarity or orientation issues where identifying features are visible
  • Visible solder bridges or an insufficient or excessive solder condition
  • Raised component ends, commonly called tombstoning

These are possible inspection targets, not a guarantee that every setup detects every defect. Inspection coverage depends on the board and the validated inspection program. Flagged locations also need review before a disposition is made.

Board geometry can make optical inspection difficult. Shadows and reflections may affect measurements of visible joints, while joints concealed beneath a component cannot be treated as directly inspected simply because the board passed AOI. These optical limitations are discussed in OMRON’s research on optical measurement and its discussion of visually inaccessible joints.

An AOI result does not establish that firmware starts correctly, a communication interface responds, or a sensor produces an acceptable output. Those behaviors need defined functional checks.

What Does FCT Check?

FCT evaluates whether an assembled board performs specified functions under defined test conditions. The board is operated according to a test procedure, and its responses are compared with agreed acceptance criteria. The exact procedure depends on the circuit and its intended use.

Items to consider in a project test specification include:

  • Power-on behavior and permitted voltage or current measurements
  • Controller startup and the required firmware version
  • Communication interfaces and expected responses
  • Inputs, outputs, sensors, and the main functions relevant to the design

Specify which of these checks apply, how they are performed, and what constitutes a pass. Do not assume a generic FCT label includes every interface, operating mode, or fault condition.

A passing FCT result supports the functions and conditions actually tested. It does not by itself establish the visual acceptability of every solder joint or prove performance outside the agreed procedure.

AOI and FCT at a Glance

AOI: Assembly Appearance

  • Main question: Are the inspected components and visible solder features acceptable?
  • Input to define: Inspection locations and appearance acceptance criteria.
  • Main limit: Optical visibility and program coverage; it does not verify board operation.

FCT: Defined Board Behavior

  • Main question: Does the board perform the specified functions under the stated conditions?
  • Input to define: Test procedure, firmware, fixture, measurement limits, and expected responses.
  • Main limit: Functions and conditions outside the procedure are not established by the result.

The two methods address different parts of the quality plan. Decide which checks are needed from the product requirements and assembly risks, rather than using one method as an automatic substitute for the other.

What Should You Provide Before Testing Is Planned?

Define the Functions and Acceptance Criteria

List the functions that must be verified before shipment. For each check, identify the setup, measurement or response, and pass/fail criterion. Provide the relevant product requirements instead of asking the manufacturer to infer acceptable behavior from a board photo.

Identify Firmware and Configuration

State whether programming is required. Identify the firmware release, programming files and method, configuration parameters, and verification requirements. If serial numbers are involved, explain how they should be assigned and checked. Programming and functional verification should be described separately so their scope is clear.

Clarify Fixture and Procedure Availability

Explain whether a test fixture and procedure already exist, who will supply them, and which revisions apply. If they are not yet available, identify that gap before a test scope or schedule is agreed. Changes to the board, firmware, fixture, or test program should be reviewed for their effect on the procedure.

Agree Quantity, Records, and Failure Handling

Confirm whether the specified tests apply to every board or to an agreed sample. Also define the required report format, failure codes, serial-number or batch records, and handling of failed assemblies. A plan for rework should include the required retesting before release.

A Checklist for Your PCBA Test Inquiry

  • Board identity and revision
  • Functions to verify and the applicable acceptance criteria
  • Required inspection and test methods
  • Firmware, programming, and configuration requirements
  • Available fixture and test procedure, with revision details
  • Testing quantity or sampling requirements
  • Result records, traceability, and failure-handling requirements

A clear specification gives both sides a basis for reviewing feasibility and the requested scope. It also makes it easier to identify requirements that still need an engineering decision.

Frequently Asked Questions

If a Board Passes AOI, Does It Still Need FCT?

An AOI pass does not prove that the board functions correctly. Whether FCT is required, and what it should include, must be decided from the project requirements.

Does Testing Every Board Mean Complete Fault Coverage?

Testing every board describes how many units receive the specified procedure. It does not establish that the procedure detects every possible defect. State both the quantity tested and the functions or inspection items covered.

Is FCT the Same as In-Circuit Testing?

No. In-circuit testing (ICT) focuses on electrical checks at component or circuit-node level, subject to the design and test access. FCT addresses the overall behavior defined for the board. A test plan should name the methods actually required. Keysight explains this distinction between ICT and functional testing.

Discuss Your PCBA Test Requirements with RONGHE

When you contact RONGHE, include your board revision, required functions, firmware details, and any existing test procedure or fixture information. Explain which inspection and test requirements still need to be defined.

Contact RONGHE about your PCBA project

Technical References

What Files Do You Need for a PCBA Quote?,www.rohepcba.com
Previous
What Files Do You Need for a PCBA Quote?
Read More
How to Choose an Analog FPV Camera: W12 Specs Explained,www.rohepcba.com
Next
How to Choose an Analog FPV Camera: W12 Specs Explained
Read More