PCB assembly functional testing: define test targets and coverage first
Testing services start by defining what must be demonstrated. Bare PCBs, PCB assemblies, and complete units have different test targets; visual, hidden-joint, electrical, functional, aging, and environmental checks each serve different purposes and cannot replace one another.
Check blind spots when selecting test methods
| Method | Suitable for Inspection | Key Boundaries | Required Inputs |
|---|---|---|---|
| Visual inspection / AOI | Visible components, polarity, position, and solder joints | Cannot inspect all hidden solder joints or validate functionality | Critical reference designators, acceptance conditions, and imaging/inspection requirements |
| X-Ray Inspection | Evidence of geometry and connection defects in some hidden solder joints | Cannot independently establish all functionality or long-term reliability | Package, critical defects, methods, and sampling |
| ICT or Node-Level Electrical Testing | Accessible nets and electrical relationships of some components | Coverage depends on accessible test points, fixtures, and test programs | Nodes, fixtures, parameters, and limits |
| Functional Testing (FCT) | Specified power, loads, interfaces, and software states | Operating conditions not exercised by the test remain unverified | Test cases, stimuli, configuration, and pass/fail limits |
| Aging/Environmental verification | Variations under specified stress and conditions | Passing the current test cannot establish an arbitrary service life | Sample configuration, conditions, monitoring, responsibilities, and reports |
Test cases must have reproducible conditions
At minimum, specify power, load, input stimuli, expected responses, limits, firmware/configuration, test software, and result fields. Calibration or error-sensitive items also require measurement instruments, references, and stable conditions. Confirm at order acceptance whether equipment is in-house, outsourced, or customer-operated, and who provides fixtures/software.
Control board test matrix example
| Use Case | Conditions and Excitation | Acceptance and Records |
|---|---|---|
| Power On | Customer defines power supply range and status | Current/startup response must meet product limits; saying it lights up is insufficient |
| Interface | Specify protocol, port, and analog load | Response, error handling, and port coverage |
| Programming | Approved firmware, configuration, and verification method | Version, checksum, board number, or SN association |
| Protection/Anomaly | Controlled fault injection and authorized test environment | Trigger/recovery conditions and retest results |
Separate sample validation, production inspection, and reliability
Samples can use more comprehensive cases to explore issues, while volume outgoing tests focus on sustained coverage and cycle time; reliability validation requires separate agreement on sample quantity, configuration, and stresses. Link inspection records to revisions, batches, and software, and clearly describe anomalies and post-repair retesting. PCB HALT/CAF and service-life claims cannot be recast as mandatory PCB assembly incoming tests or an arbitrary complete-unit service-life guarantee.
Aging, dielectric withstand, waterproofing (such as IPX7 immersion testing), vibration, and optical tests must match product objectives. Confirm instrument measurement ranges, fixtures, conditions, and reporting scope during RFQ; confirm AOI, SPI, X-Ray, and ICT separately against actual inspection-coverage requirements.
Choose the next test-planning step
Factory inspection planning: Convert test method to acceptance sheet.
Quality Management: Define sampling, exceptions, and release.
Box build and assembly: plan checks before and after mechanical integration.
Engineering reference | IPC soldering processes and assembly acceptance: agreeing on inspection criteria. A basis for methods and selection; not evidence of Qipcba capabilities
Engineering reference | BGA assembly methods: pad definitions, warpage, and hidden solder joints. A basis for methods and selection; not evidence of Qipcba capabilities
Test scope and delivery responsibilities
The following is a project requirements review checklist. Programming and functional testing are confirmed services; confirm each other specific method, equipment suitability, and coverage item individually. The list does not imply default equipment availability or provision of every service.
| Categories and requirement items | Customer input and preparation | Coverage, judgment, and recording |
|---|---|---|
| Process inspection: SPI, AOI, visual inspection | Provide BOM, pick-and-place files/CPL, assembly drawings, and revisions; both parties confirm inspection programs, first-article samples, and process standards. | Document sampling or full inspection, inspection points, and defect criteria in the inspection plan; agree on first-article and process records, and have the manufacturer release products against approved standards. |
| Hidden solder joints and structures: specialized inspection such as X-Ray | Provide packages, critical solder joints, and structural requirements; confirm equipment suitability, samples, and inspection programs. | Agree on sampling ratios, detectable defects and limitations, criteria, and image records; both parties review uncovered items, without treating the inspection as a commitment to all solder-joint reliability. |
| Electrical and functional: ICT/flying-probe testing, FCT, programming, calibration | Provide netlists, test points, interfaces, power, firmware revisions and checksums, functional cases, and calibration requirements; agree on parties responsible for fixture and software development, acceptance, and maintenance. | Confirm feasibility, sampling or full inspection, test coverage and blind spots, limits, and revision records item by item; engineering confirms programs, manufacturing executes them, and the customer approves product acceptance requirements. |
| Product-specific: aging, dielectric withstand, vibration, immersion | Define the tested product, operating state, load, voltage, duration, temperature/humidity, and other applicable conditions; confirm samples, tooling, and test procedures. | Agree on sampling, acceptance criteria, exception handling, and delivery records; distinguish internal inspection records from third-party certification reports. Equipment names do not establish product certification. |
Confirm test plans, fixture and software lists, sampling plans, report formats, and release responsibilities in the order; changed conditions require renewed approval. Test results cover only agreed targets, conditions, and items.
Specify the coverage and delivered record
| Work area | Inputs or responsibility | Expected output |
|---|---|---|
| Inspection | Visible or imaged assembly features | State inaccessible features and sampling conditions |
| Electrical or functional test | Nodes, interfaces and behavior under stated conditions | Name limits, fixtures, software and uncovered behavior |
| Programming | Approved image, configuration and device identity | Record version and verification result |
| Failure | Affected unit, symptom and disposition authority | Agree containment, repair and retest records |
Use the inspection and test comparison to prepare the discussion. Unknown inputs should be listed as open questions; they do not authorize substitutions, omitted tests or unrecorded design changes.
Example of a test record a buyer can request
Illustrative form, not a completed Qipcba customer test or an assurance of available equipment. Agree the product-specific method, fixture, limits, sample size and record format before quoting. The same unit ID must follow inspection, electrical test, programming, functional test and any rework.
| Requested evidence | Example record field | Coverage limit to state |
|---|---|---|
| Visual and assembly | Board revision B; unit U-001; inspection image IDs; visible polarity and placement checks | Visible inspection cannot establish a QFN center-pad or BGA hidden-joint connection. |
| Hidden-joint review | Selected package/region, approved imaging or other method, image ID, criterion and reviewer | Mark unobserved pads and method sensitivity explicitly; no method is assumed to be supplied. |
| Power and firmware | Fixture revision, supply/load conditions, rail readings, firmware image checksum and programming result | A rail or startup pass does not isolate every ball, via or solder joint. |
| Functional behavior | Input stimulus, output limits, environmental state, software/log version, observed result | List excluded modes, temperatures, interfaces and duration; do not imply full product qualification. |
| Failure or rework | Original symptom, unit/lot, disposition authority, changed item, post-rework retest IDs | Keep the original failure and post-rework state linked to the same unit ID; passing retest covers only the named checks. |
For a reviewable quote, send the board revision, BOM, accepted limits, expected throughput, fixture/software responsibility, sample quantity and desired evidence format. See the QFN center-pad review sheet, BGA ball coverage record and solder defect experiment for the different questions each record answers. Request a quote with your proposed test matrix.
