
Functional Test Service
PCBA Functional Test (FCT) Services
Confirm what will be powered, stimulated, measured, and recorded before the fixture is released. APTPCB builds the FCT setup around your approved firmware, loads, interfaces, limits, and production acceptance criteria.
Get an Instant Quote
Functional test
What Is Functional Circuit Test (FCT)?
| Question | Answer |
|---|---|
| What is functional circuit test? | Functional circuit test (FCT) powers an assembled board and checks that it behaves as designed — firmware boots, interfaces communicate, sensors read within range and outputs drive their loads. |
| How is FCT different from ICT? | ICT checks accessible components and nets and can include powered checks or programming when the setup supports them. FCT checks the defined operating behavior, including firmware responses, timing and loads covered by the approved plan. |
| When does FCT earn its cost? | When a board must be proven functional before shipment, when downstream assembly cost makes a late failure expensive, or when the product is safety- or mission-relevant. |
Coverage matrix
What Does PCBA Functional Testing Cover?
| Product function | Typical FCT checks | Customer baseline | Possible result record |
|---|---|---|---|
| Power and startup | Rail presence, sequencing, reset, boot, inrush, and steady-state current | Nominal rails, timing, load state, and acceptance limits | Pass/fail, measured voltage or current, and failed step |
| Digital control and firmware | Firmware identity, boot state, GPIO, modes, commands, and fallback behavior | Approved image, programming method, expected states, and version rule | Firmware version, state result, error code, or response |
| Communication interfaces | UART, RS-232/485, I2C, SPI, CAN, LIN, USB, or Ethernet exchange where applicable | Protocol, command set, peer device, test data, termination, and timeout limits | Link status, response, data check, timeout, or failed transaction |
| Analogue and sensor paths | Stimulus, ADC reading, reference voltage, gain, offset, and range response | Stimulus source, calibration basis, test points, tolerance, and environment | Measured value, limit, channel, and pass/fail result |
| Outputs and loads | Relay, MOSFET, motor, fan, LED, display, buzzer, and other output behavior | Load or simulator, drive sequence, duration, expected output, and safe limits | Output state, measured level, timing, current, or failed step |
| User I/O and interlocks | Buttons, indicators, connectors, enable lines, and defined safety interlocks | Input sequence, expected feedback, fixture access, and acceptance criteria | Sequence status, response, operator prompt, or exception code |
A listed interface or function is not automatic coverage. Confirm the fixture, stimuli, peer devices, firmware, limits, sampling, and report fields for the actual order.
Engineering review to production release
When Is a Functional Test Fixture Worth Building?
Fixture and golden-board baseline
Test software and result handling
Pilot validation and limit tuning
Production release and change control
In-house fixture and test program
Who Builds the FCT Fixture and Test Program?
| Stage | APTPCB (in-house) | Customer | Evidence released |
|---|---|---|---|
| Requirements | Map functions, stimuli, loads, interfaces and required records to a test plan | Provide functional specification, expected outputs and limits | Approved test-plan revision |
| Fixture design | Mechanical and electrical fixture design, probe and connector selection, strain relief and access strategy | Confirm board orientation, connector definitions and handling constraints | Released fixture drawing and wiring schedule |
| Fabrication and assembly | Machine and assemble the fixture in-house; verify contact force, alignment and connector keying before the first board is loaded | Approve any deviation from the agreed fixture concept | Fixture build record and pre-load check |
| Test program | Develop power-up, stimulus, measurement, comparison and error-code logic, and define result storage | Supply the approved firmware image and programming method | Released program version tied to a firmware revision |
| Golden board baseline | Check the fixture against known-good behavior and tune timing and thresholds | Provide a golden board where available, or approve reference behavior in writing | Pilot results and limit justification |
| Release and change | Release fixture, program and work instruction under revision control | Approve coverage, limits and any later change | Production release package |
Where a fixture is customer-supplied or a legacy jig is reused, the same table applies — the responsible party changes, and that change is recorded in the quotation rather than assumed.
Acceptance before tooling
Which FCT Requirements Need Approval Before Fixture Release?
| Requirement to clarify | Approve before fixture release | Confirm in the RFQ |
|---|---|---|
| Power and current | Supply and load state, firmware revision, measurement point, settling or measurement window, and allowed range. | Who supplies the operating-state instructions and approves the current limits? |
| Communication works | Peer device or simulator, commands, expected responses, timeout and data checks. | Who supplies the protocol details, peer hardware and firmware needed for the exchange? |
| Output drives its load | Load or simulator, drive sequence, duration, measured response and safe limits. | Who supplies the load definition and hardware, and approves any simulated replacement? |
| Matches a golden board | Approved requirement and limits, reference identity, and how the reference is checked. A golden board supports comparison; it does not establish acceptance limits. | Who provides or approves the reference, resolves mismatches and authorizes limit changes? |
Include requirement IDs and unresolved acceptance questions with the RFQ. Agree resource supply, setup validation and approval responsibilities before releasing the fixture and program.
Behavioral failures
Which Defects Can FCT Catch After Assembly?
Power is present, but the board does not boot
The interface connects, but transactions fail
An output changes state but cannot drive the required load
Sensor or measurement channels respond outside range
Test-method selection
PCB Functional Test vs ICT: Which Do You Need?
| Method | What it primarily checks | Important boundary | Typical role |
|---|---|---|---|
| AOI | Visible component presence, polarity, placement, solder, and workmanship features | Cannot prove hidden joints or product function | In-line assembly inspection before later electrical or functional tests |
| X-ray inspection | Hidden solder-joint and internal assembly features within the defined inspection scope | An image does not prove circuit behavior | Inspection of BGA, QFN, bottom-terminated, or otherwise hidden features |
| ICT or flying probe | Accessible nets, continuity, shorts, and selected component relationships | Coverage depends on test access and does not replace powered product behavior | Electrical assembly-defect screening before or alongside FCT |
| FCT | Powered response to approved stimuli, loads, firmware, interfaces, and sequences | Only the released test plan, conditions, and limits are verified | Product-specific behavior verification and production release evidence |
Use the PCBA testing and quality hub to map inspection and test layers to design access, production volume, failure risk, and required evidence.
Functional test planning
PCBA Functional Testing Service: Questions Before RFQ
What information is needed to quote PCBA functional testing?
Does every FCT program require a golden board?
Can APTPCB develop the FCT fixture and test program?
Can the same FCT setup support prototypes and volume production?
Do I need FCT if the assembly already has ICT?
What records can be delivered with FCT?
Does an FCT pass replace product qualification or certification?
Is the functional test fixture built in-house or subcontracted?
Records and RFQ closure
What Should an FCT Test Report Contain?
RFQ inputs
Qualification boundary
| Record field | Purpose |
|---|---|
| Board or lot identity | Connect the result to the agreed serial number or lot method |
| Test date and revision | Identify when the test ran and which released program or plan applied |
| Pass/fail and failed step | Show the disposition and isolate the point of failure |
| Measured value and limit | Retain parametric evidence where the approved test records it |
| Repair and retest status | Close the nonconforming-board flow under the order procedure |
Record availability, format, sampling, and retention depend on the released test plan and order.
Before tooling approval
Get an FCT coverage and fixture review
Send the available schematic, BOM, firmware, functional specification, expected loads, acceptance limits, golden-board status, and reporting needs. We will confirm practical coverage and quote assumptions before tooling release.