What DFT covers
A production test can only check what the design lets it reach. DFT is the set of design decisions that give the factory that access: test points on the board, programming and debug interfaces, test modes in firmware, ways to measure and calibrate sensors and radios, and a way to identify and log every unit.
In semiconductor design, DFT refers to on-chip structures such as scan chains and built-in self-test. This entry covers board and product level DFT, the part a hardware team designs together with its EMS or OEM/ODM partner.
How DFT connects to production test
Electronics are usually tested in layers, and the design has to serve each one:
| Test stage | What it checks | What the design must provide |
|---|---|---|
| Optical (AOI) and X-ray inspection | Component placement and solder joints | Joints the camera can see, clearance around parts, and X-ray for hidden joints |
| ICT or flying probe | Shorts, opens, component values | Test points on key nets that probes can reach |
| Boundary scan (JTAG, IEEE 1149.1) | Connections on dense digital boards | Compatible devices and an accessible scan chain |
| Programming | Firmware, keys, serial numbers | Programming pads or a connector, and a defined process |
| FCT | Board or product functions | Test firmware, test modes, reachable interfaces |
| Calibration | Sensor and radio accuracy | Calibration routines and storage for the results |
| Final system test | The finished product as a user sees it | A way to test after the enclosure is closed |
| Burn-in, where used | Early-life failures | Self-test or logging modes |
DFT decisions to make during design
- Test points: place them on power rails, key signals and interfaces, sized and spaced to the fixture supplier’s rules. Agree those rules with the factory before layout, not after.
- Programming: decide how firmware and security keys are loaded: through pads and a pogo-pin fixture, through a connector, or by buying pre-programmed parts. Each choice affects cost, cycle time and security.
- Test firmware: plan a factory test mode that exercises every function and reports results to the test station. Test firmware is a deliverable with its own schedule.
- Sealed products: if the finished product is sealed or waterproof, plan how it will be tested and updated once closed, for example through a wireless test mode or external contacts.
- Radio and sensor test: decide which measurements happen on the board and which on the finished unit, and whether shielded test enclosures are needed.
- Traceability: give every unit a unique ID and make sure results are logged against it.
Test coverage
Coverage is the share of possible defects the combined tests can detect. No production test catches everything, so the real question is which defects you accept letting through, and at what cost. Ask the factory to map each known failure mode, from the design FMEA or earlier builds, to the station that would catch it. Gaps in that map are where field failures come from.
Common DFT mistakes
- Removing test points to save board space. Late layout compaction often deletes the access production test needs.
- Starting test development after DVT. Fixtures and test software take time to build and debug; when they arrive late, PVT runs on incomplete tests.
- Relying on a power-on check. A unit that boots can still have a weak solder joint, an out-of-tolerance sensor or a poorly tuned antenna.
- Not logging results. Without per-unit test data, field failures cannot be traced back to a station, a lot or a date.
Where Zefinity helps
Testability is cheapest to fix before the layout is final. Zefinity’s Develop service includes technical advisory while the design is still open, and during NPI the Launch service provides manufacturing engineering support alongside the factory’s test team. See Develop: prepare your product for manufacturing and Launch: navigate NPI and scale production.
Frequently asked questions
Who designs the production test?
Responsibility varies and should be written down. Commonly the brand defines what must be tested and the pass limits, the factory or a fixture supplier builds the fixtures and stations, and the firmware team supplies the test firmware. When nobody owns the overall test plan, coverage gaps go unnoticed until units fail in customers' hands.
Does DFT add cost?
Some. It takes board area for test points, money for fixtures and time for test firmware. It usually saves more by stopping defective units from shipping and by making failures diagnosable. The balance depends on volume and on the cost of a field failure, which for connected or battery-powered products is often high.