Upload BOM & Gerber
-
Mobile: +86 13312967631
-
Email: info@sugaintl.com
PCB In-Circuit Testing (ICT) Services
Fixture-Based ICT Testing from a PCB Assembly Manufacturer in China
SUGA offers printed circuit board (PCB) in-circuit testing to support stable versions of PCB assemblies produced using repeatable assembly methods and tested consistently using fixtures. The process begins with validating that the electrical fixture checks match the board data and the defined test access limits before the fixture setup takes place.
ICT checks to confirm before fixture work
- Validate fixture setup against released board data
- Validate test access points before fixture setup
- Validate pass/fail limits against expected results
- Define scope of work before fixture setup
What ICT Testing Checks in a PCB Assembly Build
In the PCB assembly process, electrical fixture checks involve testing the assembly using test probes on specific test connections to measure the electrical responses of the completed PCB assembly. These checks can be performed against continuity, resistance, capacitance, diode behavior, or component presence when the PCB design, access points, and pass/fail limits allow the process to produce the electrical test results.
ICT as a Fixture-Based Electrical Check
ICT is typically used when PCB assemblies have stable, repeatable designs and electrical test access points are available on the finished assembly. Instead of evaluating the completed PCB assembly based on powered product operation, the ICT fixture evaluates specific nets and components on the assembled board with dedicated test probes and specific test programs. ICT can also provide information on potential electrical failures before the PCB assembly process moves further.
Where Fixture-Based Checks Stop
An ICT test result is based on access to the circuit; it provides electrical evidence, not a conclusion for every physical issue. A flagged signal may be due to a solder joint, component value, trace condition, pad issue, or fixture contact state. The meaning of the ICT result is determined by actual probe access, circuit performance, program limitations, and any post-test follow-up to be completed for the project.
When ICT Fits a Stable Board Revision
ICT becomes beneficial when a fixture supports electrical testing that can be made repeatable and does not create unnecessary rework. The main question is not whether there is a tester available to perform testing, but whether the board is stable enough for the fixture and testing program to remain effective.
Revision Stability Before ICT Fixture Work
When a design revision is complete and locked, with no pending engineering change order (ECO), the main components are stable or not expected to change, and test points have been identified and are ready to be worked with. Fixture and testing programs should be developed based on that stability.
If the design is not locked or stable, or if there are risks associated with layout changes or component changes, fixture work is subject to further rework costs linked to new layouts or fixture updates.
Check Whether the Target Nets Are Reachable
If there is no available physical contact at the critical routing lines or nets, the test label alone is not enough to define coverage. The best starting point is identifying which risks can be checked through accessible test points, and which risks may require a different check approach or an additional verification step after final assembly.
When Fixtureless or Functional Testing Fits Better
Repeat orders or future quantity forecasts make it easier to justify a fixture investment because it can support similar checks. For prototype boards, low production quantities, or changing revisions, fixtureless electrical testing options may be used before investing in dedicated fixture work.
When firmware response, load behavior, communication, or product operation is an overall concern, using ICT as one part of the test plan can support checking both component-level and net-level conditions, but functional testing combined with ICT may be appropriate in some situations as part of a broader test plan.
What ICT Fixture Review Needs Before Setup
An effective fixture review is only possible when the most up-to-date Gerber, BOM, placement, test-point map, and board revision information is available to evaluate. If released files are not consistent with one another or if revision status is unclear, then fixture-program development will be conducted based on incorrect access points, incorrect component values, and incorrect test expectations.
The goal is to identify setup blockers before beginning fixture work: no access, component data needing clarification, insufficient clearance, or limits to be confirmed.
Files and Board Conditions Needed for ICT Fixture Preparation
| File or Board Detail | Used For | Fixture Check | If Missing |
|---|---|---|---|
| PCB Outline and Panel Drawing | Size of Fixtures, Support locations and contact positions on the panel | PCB Seating Area and PCB Support Area | Poor PCB Support During Probing |
| Test Point Map | Planning for Probe Positions | Access to Test Pads, Vias and Other Test Contacts | Nets without contact points may fall outside ICT scope |
| Most Recent Gerber File | Availability to Align the Fixture to the Released PCB File | PCB Pad Position, PCB Edge and Tooling Hole Location | Mismatched Fixture After Changes Made to the PCB Layout |
| Component Placement File | Determining Clearance on the Probe Side for Tall Parts, Dense Areas and Contacts | Access to Probe Blocked by the Component | Probe-Side Clearance May Be Misjudged |
| Component Height Data | Planning for Keepouts and Relief on the Probe Side | Height on the Probe Side and PCB Support Side | Possible Interference from the Fixture |
| Forecast Quantity | How Much the Fixture Will Cost to Build and How Suitable for a Repeat Build | Repeat-Build Suitability | Flying probe testing may fit low demand or changing demand better |
Layout, Gerber, BOM, and Revision Data
If the layout or component locations change after fixture work begins, probe access and fixture alignment may need to be re-evaluated.
Test Access, Clearance, and Fixture Inputs
ICT requires that fixture probes reach each designated location for testing with no mechanical interference, so component clearances, solder-side conditions, and available pads must be taken into account when confirming selected-net access for fixture testing. Once probe contact is confirmed, it will be important to define not only fixture feasibility, but also which electrical risks may be verified through those points and which will require verification via another testing method.
From Access Points to Agreed Pass/Fail Limits
After access is confirmed, you will need to develop pass/fail criteria for your test program. The pass/fail limits indicate the acceptable range for which a measured result will be considered passed or failed. The pass/fail limits must agree with the design specifications of the circuit, the component data, and the test intention of the assembly.
Unclear pass/fail limits will create unnecessary debugging. The assembly may be physically accessible, but the fixture setup is not configured for repeated use until the expected responses and pass/fail criteria are verified against the submitted assembly data.
Fault Signals ICT Can Flag and How to Read the Result
When the test program permits and access allows, ICT can detect problems with an electrical circuit and flag them. Fault signals flagged by ICT could include continuity failure or abnormality, net-to-net short, missing or incorrect component value, and selected orientation-related signals. Reading a fault signal depends on how the signal is measured and reviewed after the first fault is detected.
ICT Fault Coverage and Result Limits
| Test Focus | Typical Fault Found | Needed Condition | What ICT Does Not Prove |
|---|---|---|---|
| Continuity | Open Circuit Faults | Reachable Exposed Test Points | Cannot Identify Exact Cause of Open Circuit |
| Net Isolation | Short-Circuit Faults | Defined Test Program | Unknown If Shorting Condition Caused by Solder, Component, or Design |
| Resistor Value | Incorrect Resistor Value | Measurable Circuit Path | Value May Be Affected by Parallel Components |
| Capacitor or Inductor Values | Incorrect Capacitors or Inductors | Guarded Path for Measurements | Cannot Prove Full Standalone Component Performance |
| Diode Polarity | Reverse Polarity Signal | Exposed Polarity Path for Probes | Cannot Check Visual Polarity Mark or Orientation |
| Missing Components | Path Open or Out of Range Reading | Electrical Path Affected by Missing Components | Parts with No Measurable Electrical Path |
| Powered Behavior | Firmware, load, interface, or system response issue | Powered FCT or defined fixture add-on required | Standard ICT does not prove firmware, load, interface, or system behavior |
From Fault Signal to Measured Response
ICT readings need to be interpreted through the measured path, not only through the fault name.
When measuring components, an ICT reading can differ from a bench measurement of the same component. If the measured component has other conductive connections in parallel, the ICT system will read the component value as part of the actual circuit. For instance, if two resistors are connected in parallel, the total resistance in the circuit can be lower than either resistor alone. If this happens, the reading from the ICT system will require additional analysis before classifying it as a confirmed faulty component.
Why Some Readings Need Debug
Three factors can require closer review of ICT readings: 1) system-specific physical factors, 2) other circuit elements that influence the measured path, and 3) low or marginal signals caused by limitations in the path to the ICT system.
Guarded measurements can reduce the influence of other parallel circuits connected to the measurement path. A guarded measurement can improve measurement isolation, although it may not guarantee that the final measurement will be limited to only one item under all test scenarios.
What an ICT Result Cannot Prove by Itself
A flagged signal points to an area for investigation, not the root cause. The ICT test could indicate that there is an open on a connector net, but the cause could be a missing solder joint, a cracked trace, a lifted pad, pad contamination, or an issue with the fixture contact.
Polarity results also need the same level of caution. The ICT test could identify certain diode, LED, or transistor orientation-related electrical signals because the fixture, program, and access are set up correctly to check these orientations, but it does not prove every orientation or polarity issue.
Why a Pass Result Still Needs Context
When a product has passed the ICT test, this means that the tested nets, along with intended checks, have passed within the limits that were agreed upon in the fixture program. A passing result from the ICT program is not considered full product validation, confirmation of expected behavior, acceptance of solder joints, or hidden-joint inspection.
Further steps may include visual inspection, automated optical inspection (AOI), X-ray inspection, functional circuit test (FCT), fixture/program debug, or engineering follow-up based on the type of signal, component package type, probe access, and what else needs to be proven before the build continues.
What Drives ICT Testing Cost and Preparation
Many factors beyond the test method influence ICT cost. For instance, costs associated with initial fixture setup, the maximum number of tested nets, the stability of the revision, available probe access and the time required for debug can affect ICT cost and preparation. Fixtures that have a high count of tested nets can affect the design of the fixture contact, program setup, and debugging time. While the test method used remains the same, the pricing basis for the test could change.
The preparation for the ICT test can also change when the test limits are unclear, the revision of the board is still in transition, or probe contact must be verified more closely to ensure proper contact is being made to the board. In these instances, preparation before repeat testing will not be limited to a simple release of the program.
Cost and Lead-Time Drivers for ICT Testing
| Cost Driver | What It Affects | Review Input | Cost / Lead-Time Impact | Quotation Risk |
|---|---|---|---|---|
| Fixture Build | Tooling Cost – Set up and prepare time for the fixture | board size and panel format/test-point count/probe-side access | requires more labor for fixture setup and repeat testing | the cost of the fixture may not fit into a build for an unstable or very low-volume build |
| Tested Net Count | Scope of programming setup and debugging | target ICT scope, summary of netlist, total number of nets tested | More contacts, access checks, and debug time are required | some nets may fall outside test coverage |
| Test Limit Table | Clearer limits for pass/fail and troubleshooting | Approved resistors, capacitors, diodes, etc. | Clearer limits reduce debug time caused by poorly defined limits | Tight/unclear limits create false call-outs |
| Board Revision Change | Review of the fixture and program for an ECO | updated information for the most current revision of PCB and BOM | Revision control is critical | if not followed, the fixture and program will not match |
| Component Density and Access | Stabilizing of the probe contact and fixture | an extra review of probe-side height due to placement density | further access reviews may be necessary | contact retry or fixture relief may be required |
| Production Forecast and Powered Add-Ons | Justification for fixture cost and added coverage for FCT | forecast quantity, firmware requirements, load conditions, communication needs, and FCT protocol | The coverage may go beyond the standard ICT scope | Flying Probe or FCT may be more appropriate when repeat use doesn't justify the cost of a fixture |
Fixture Work and Tested-Net Count
Tested-net count is only one indicator of fixture effort, not a complete measure of the setup required.
In some cases, boards with more complex component layouts may require a more concentrated set of access checks than larger boards with more evenly spaced access check points. The key consideration is the number of access points, fixture contacts, programmed checks, and debug checks that can be completed reliably.
Limits, Revisions, and Debug Effort
Clear test limits reduce false calls and debug time by keeping the fixture and test program aligned with component data and circuit behavior.
Stable release data also reduces preparation delays when a component, layout, or test point changes between revisions.
Probe Access, Forecast, and Powered Add-Ons
Access-related factors may indicate the need for review before pricing or fixture work continues.
There is no direct formula for defining a break-even point; the decision is tied to future assembly expectations, design stability, and the level of risk the ICT process is expected to mitigate.
ICT programs may contain added powered testing levels, programming at the fixture, or limited signal check and verification levels. Since these items expand the basic electrical fixture coverage, they require coverage review during the pricing phase. These additions will also be reviewed to confirm ICT fit for the assembly.
Choosing Between ICT, Flying Probe, FCT, AOI, and X-ray
When there is a stable board revision, accessible test points, and established demand for a fixture-supported checking approach, ICT is often a practical fit. In other applications where physical component-level electrical testing is not achievable or the electrical checking requirement does not align with the assembly requirement, other test methods may be more effective.
Test Method Fit: ICT, Flying Probe, FCT, AOI, and X-ray
| Test Option | Best Use | Fixture Needed | Main Check | Not Designed For |
|---|---|---|---|---|
| ICT | Stable PCB Builds with Test Access | Bed-of-Nails Fixture | Opens, Shorts, Component Values, Specific Polarity Signals and Missing Components via Open or Out-of-Range Readings | Full Product Function |
| Flying Probe Testing | Prototypes, Low-Volume Designs, or Changing Revisions | No Dedicated Bed-of-Nails Fixture | Opens, Shorts and Targeted Component Checks | High-Volume Production That Needs Short Per-Board Test Time |
| FCT | Powered Board or Product-Level Testing | Test Fixture, Cable, or Product Test Setup | Validation on Power Up; Signal Response; Communication; Load Characteristics | Component-Level Fault Isolation |
| AOI or Visual Inspection | Review of Surface Mounted Assemblies | Optical Inspection Setup | Positioning; Appearance of Solder; Visual Markings for Polarity Orientation | Electrical Continuity Test of Each Assembly |
| X-Ray Inspection | Hidden Solder-Joint Review | X-Ray Inspection Setup | BGA, QFN, LGA, or Hidden Joint Quality | Verification of Powered Functional Behavior; Component Parametric Values |
Selection should start with the failure concern that requires evidence. If the primary concern is component-level electrical faults on a stable design, ICT is a practical starting point. If the design is not yet final or no fixture is ready, flying probe testing may be considered before fixture cost is committed.
If the failure concern relates to power-on behavior, load response, or communication checks, FCT usually provides the best match. If the failure concern relates to solder appearance, placement, polarity visibility, or hidden solder joints, then optical or X-ray inspection should sit alongside electrical testing and not as a replacement.
A valid test plan does not assume that passing one test proves the entire product. Instead, a good test plan pairs each area of evidence with the matching test method: electrical signal testing using a fixture, using fixtureless testing for new or changing designs, functional testing for the response of the active circuit, and some method of inspection for physical evidence of solder joint or placement.
Check ICT Readiness with a PCB Assembly Supplier in China
Confirm that the PCB assembly supplier in China has reviewed the PCB requirements and your project stage before you ask them for advice on ICT feasibility. Once you have this information, and the intended tested scope, accessible probe points, and test intent are presented clearly enough to define the fixture approach, SUGA will be able to provide a more specific response.
ICT Readiness Checks Before Fixture Review
The items below provide the basis for your preliminary discussion around the ICT process:
- Is the current board revision stable enough for fixture review?
- Are the fixture probes able to reach the intended test points?
- Has the expected test scope been determined?
- Is only unpowered testing required, or will powered add-ons also be required for the project?
- Have you provided sufficient assembly quantities or forecast information to allow pricing context to be created?
These checks help determine request readiness, information gaps caused by limited access, or the need to review another testing approach before committing resources to a fixture.
Files to Send for ICT Quotation Review
After you have determined that the design has reached a stable level, confirmed physical access to the test points, and established the expected electrical testing scope, you should compile and forward project files to SUGA to request a quotation. SUGA will review the submitted project files and provide either pricing direction regarding the fixture design or a list of open items before commencing fixture assembly.
Upload BOM & Gerber
Common ICT Testing Questions
An ICT test is a form of fixture-based testing for assembled PCBs targeting specific electrical parameters. The fixture probes and programmed limits allow designated nets or components to be read, and the results only represent the coverage specified for the design.
ICT testers are tools that test assembled boards through a fixture-based method. The device allows many different nets or components to be tested, depending on the application, using a dedicated fixture, test probe connections, programmed limits, fixture design, test access, and a developed test program to verify that the board is within the defined limits.
Timing for ICT testing varies by fixture readiness, intended component test scope, board stability, probe accessibility, and debug rounds. Boards that are in a stable state with properly aligned files will take less time to prepare than boards with changing designs, undefined probe accessibility, and constantly changing component layouts. Once the board data, test intent, and fixture requirements are reviewed, the expected timing can be discussed.
ICT testing can identify electrical faults at the PCB level, potentially saving time and cost later in the assembly process. Being informed of the board status from the locations of opens, shorts, and out-of-specification values can help minimize troubleshooting based solely on physical inspection before product-level testing for firmware or load operation issues.
SUGA prices ICT based on more than test type alone. The cost associated with the fixture varies by board files, tested-net count, probe reachability, programming complexity, revision stability, and anticipated repeat use. Review is needed before fixture purchase to confirm the investment fits the build.
If the PCB revision is stable and the fixture can be reused for subsequent builds, ICT will usually be more efficient. However, if you have a low-volume program, are not ready for fixture cost, or will continue to change the board, flying probe testing may serve as a better initial test solution.
Some programs need both ICT and functional testing. In general, ICT is more applicable for testing electrical responses at a component or net level; functional testing is typically focused on assessing powered operation, load conditions, or interface behavior. Many programs use one type of test to supplement the results of the other.