Test data analytics · Electronics & EMS
Test data analytics. Find where yield is lost.
Connect ICT and functional test measurements with station, retest and repair records. QualityLine helps electronics manufacturing teams see which failures deserve attention and what to investigate next.
For test engineers, quality teams and production leaders working with electronics and EMS test data.
- 01MeasurementsWhich parameter changed?
- 02Station contextWhere and when does it happen?
- 03Unit historyWhat happened on retest or repair?
- 04Engineering validationWhich explanation fits the evidence?
Manufacturing test data analysis
Look inside the pass/fail result
A final result tells you whether a unit passed. The measurements, test sequence and production context help explain the pattern. QualityLine brings those records together for investigation.
01 · Parameters
Find the measurements behind failures
Review failed test parameters and their measured values against the recorded limits. Compare the same parameter and measurement unit over time to see where results cluster or shift.
Keep product revision, test program and limit changes visible when interpreting a trend.
02 · Stations
Compare equivalent test conditions
Review station yield, failure patterns and tested volume. Start with the same product and test program, then investigate differences in fixtures, calibration, operators or production mix.
A station difference is a lead to investigate; it does not establish that the tester caused the failure.
03 · Retests
Separate first attempts from later passes
Follow the available attempt history for each unit. Distinguish a first-pass success from a pass after another test or repair, so a good final yield does not hide repeated work.
04 · Repairs
Connect the symptom with the finding
Bring failed parameters together with repair codes, component references and technician findings where matching records exist. Use that context to narrow the investigation and check recurring issues.
Inside QualityLine
See the station. Inspect the failed tests.
QualityLine product examples: compare station results, then review the failed-test breakdown. Screens shown are from June 2024; available views depend on your configuration.

Open the station screen at full size ↗

Open the failed-tests screen at full size ↗
A practical investigation
A repeat failure needs context
For example, a functional test parameter fails more often at one station, yet many affected units pass on retest. Use the pattern to organize the investigation before changing the process.
Illustrative workflow, not a customer case or an automatic diagnosis.
- 01
Define the comparison
Select a consistent product, revision, test program and period. Include the number of units tested so a small sample does not dominate the conclusion.
- 02
Review the measurement
Check the parameter, units and limits in use. Look for a shift, spread or repeated near-limit values, and confirm that the records are comparable.
- 03
Trace each attempt
Check whether a later pass followed repair, a fixture change or another test. Missing repair records leave that part of the explanation unresolved.
- 04
Validate and monitor
Have engineering test the likely explanation. After an approved change, compare equivalent groups and track first-pass yield alongside retest activity.
A pass on retest does not by itself prove a false failure. Investigate measurement repeatability and reproducibility with Gage R&R analytics when the measurement system is in question. Keep test limits tied to approved product requirements.
Prepare useful test data
Bring the result and its context
Existing test log files and database extracts can be starting points. The analysis available depends on the fields, history and access your sources provide.
- Unit and product
- Serial number or another stable unit identifier, part number and product revision where recorded.
- Station and time
- Station name or ID, timestamp, process and test-program version where available.
- Measurements and limits
- Parameter name, measured value, measurement unit, lower and upper limits, and the parameter result.
- Attempts and outcomes
- Unit pass/fail status and enough history to order test attempts. Include duration when investigating test time.
- Repair findings
- Matching unit ID, failure code, component or reference designator, repair action and timing where recorded.
- Production context
- Relevant inspection, assembly, MES or ERP records with identifiers that can be matched reliably.
Start with ICT (in-circuit test), FCT (functional test) or end-of-line results. AOI/SPI inspection can add upstream context through SMT analytics. Manual test records can also contribute when they contain usable identifiers and results.
Test analytics questions
What to know before you start
What is electronics test data analytics?
It is the analysis of test results and measurements from electronics production. QualityLine connects available test, station, production and repair records to help teams investigate failures, yield changes and repeated tests.
Can we start with pass/fail data only?
Pass/fail records can support outcome and yield analysis when unit identifiers and test history are sufficient. Parameter values, units and limits add the detail needed to investigate measurement-level patterns. Read why measurement data matters.
How should we compare different testing stations?
Compare equivalent products, revisions, test programs, limits and periods. Review sample size and production mix before attributing a difference to a station. Fixture condition, calibration and repeatability may need a separate engineering check.
How do retests affect first-pass yield?
A unit that fails its first attempt and later passes is not a first-pass success. Reliable calculation needs unit-level attempt history and agreed rules for duplicate records, aborted tests and the process boundary. See the FPY definition and counting examples.
Does QualityLine automatically change test limits?
The workflow on this page uses analytics to support investigation. It does not promise automatic changes to tester settings. Your engineering and quality teams validate findings and approve changes through your established controls.
Will it work with our existing testers?
Bring representative test records and information about the equipment, available outputs and access restrictions. QualityLine can then confirm the collection method, matching coverage and analysis scope for your environment. Compatibility is reviewed for the specific sources.
Discuss your test environment
Which test problem would you investigate first?
Start with a recurring failure, a station difference or a retest problem. In a product demo, discuss the records available and the analysis that would help your team act.
Useful context: product family, test types, station count, available history and the issue you want to understand.
