Industries / Technology / Electronics and semiconductors / Contract electronics manufacturing
Testing
This work checks each assembled board for missing, wrong or badly soldered parts, by probing it electrically, photographing it or X-raying it, before it is built into a product.
4
Milestones achieved, from 1979 to 2007.
1
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1979
Every part tested separately
An in-circuit tester presses a bed of nails, a fixture of spring-loaded pins, onto the finished board so that it touches every circuit node, then measures each part on its own. Hewlett-Packard described its 3060A board test system, built around such a fixture, in the HP Journal of March 1979. A Teradyne engineer later wrote that these testers, first introduced in the late 1970s, let test programs be generated in days instead of weeks, because the programmer no longer had to understand what the board did.
Credit
Hewlett-Packard
1987
Testers lose the fixture
A bed of nails has to be built for each board design, which by the account of the German trade magazine all-about-industries cost thousands of euros and weeks of waiting for every change. In 1987 Takaya of Japan introduced the APT2200, which the magazine calls the world's first flying-probe tester: two to four probes move over the board on motorized axes and touch test points in turn, so a new board needs a program but no fixture. It is slower per board, and it suits prototypes and the changing small orders of contract manufacturers.
Credit
Takaya Corporation; Seica of Italy followed in 1995
1993
X-rays see hidden joints
Some solder joints, such as those under ball grid array chips, are hidden from a camera. Four Pi Systems of San Diego built X-ray machines that image one slice of a board at a time (laminography); by the account of Robert Boguski in Circuits Assembly, its first model was down more often than it was up, and in 1993, near bankruptcy, Four Pi was bought by Hewlett-Packard, which developed the 5DX. Electronic Design reported in 1996 that Mitsubishi's US phone plant, after replacing visual inspection with 5DX machines, raised first-pass yield at functional test by seven percentage points and cut inspection time by more than 65%, to under 1.5 minutes a board.
Lessonan inspection method that works in principle still fails if the machine cannot stay running on a factory floor.
Credit
Four Pi Systems; Hewlett-Packard
2007
Failures that came later
On 5 July 2007 Microsoft extended the warranty on its Xbox 360 game consoles to three years for a general hardware failure shown by three flashing red lights, citing "an unacceptable number of repairs", and took a charge of $1.05 billion to $1.15 billion before tax. The consoles were built by contract manufacturers: Microsoft had named Celestica, Flextronics and Wistron, with plants in southern China, in August 2005. Microsoft said it had made improvements to the console, and ABC News reported that Microsoft declined to say what it fixed.
Lessona fault that appears only after months of use passes every test at the end of the line, and here repairing it after sale cost more than $1 billion by Microsoft's own estimate.
Credit
Microsoft
Watch for
Synthetic pictures of defects
AI inspection models need many pictures of real defects, which are rare on a good line. NVIDIA says Pegatron used its Cosmos models and Isaac Sim simulator to generate synthetic defect images, cutting the time to deploy AI visual inspection by 67% and operating effort by 10%, and that in Inventec's internal check for laptop cosmetic inspection more than 10,000 synthetic images showed potential to cut real data collection and labeling by about 30% and deployment time by about 25%.
Achieved whenPegatron, Inventec or an outside party publishes before-and-after results on production units, including missed defects and false calls, or an independent group reproduces the data savings on public images.
Claimed by
NVIDIA, for Pegatron and Inventec, May 2026
Open
01
Test coverage for KiCad boards
A free KiCad plugin that reads a board and a test plan and reports, for every part and pin, which manufacturing faults the plan would catch: a missing or wrong part, a part turned the wrong way, an open joint or a short to the next pin. The plan can mix probing of reachable test pads, boundary scan and camera inspection, and the fault list follows a published coverage model such as PCOLA/SOQ from Agilent or PPVS from ASTER.
The briefCredit · unclaimed02
Score an open flying prober
Use an open-hardware flying-probe tester built from 3D-printer parts to test unpowered assembled boards for opens, shorts and wrong resistor values, and publish how many planted faults it finds and how many good boards it wrongly fails.
The briefCredit · unclaimed
Open 01 · the brief
Test coverage for KiCad boards
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A free KiCad plugin that reads a board and a test plan and reports, for every part and pin, which manufacturing faults the plan would catch: a missing or wrong part, a part turned the wrong way, an open joint or a short to the next pin. The plan can mix probing of reachable test pads, boundary scan and camera inspection, and the fault list follows a published coverage model such as PCOLA/SOQ from Agilent or PPVS from ASTER.
Why it is still open
Coverage analysis is sold as commercial software, such as ASTER's TestWay; XJTAG's free assistant runs only inside Altium Designer and checks boundary-scan connections; the open KiCad tools we found, kicad-testpoints and KiTFG, list test pad positions or make bed-of-nails plates but compute no coverage. A Teradyne engineer wrote that shrinking boards keep reducing the room for test points, so knowing what each test misses matters more each year.
aster-technologies.comxjtag.comgithub.comgithub.comelectronics.org
Built with what exists
KiCad's Python scripting and its netlist and pad data; the coverage models described in ASTER's article; a USB multimeter, or the open flying prober in the next item, for checks on built boards.
First step
Write the fault list for one simple open board by hand and compare the plugin's first output with it.
Done looks like
coverage reports for 20 open-hardware KiCad boards, published with the code; on two of them, faults planted on built boards and found or missed as the report predicted, with every mismatch listed.
Open 02 · the brief
Score an open flying prober
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
Use an open-hardware flying-probe tester built from 3D-printer parts to test unpowered assembled boards for opens, shorts and wrong resistor values, and publish how many planted faults it finds and how many good boards it wrongly fails.
Why it is still open
Open projects exist, such as apertus's pcb-prober (2020), built from 3D-printer mechanics, and GainSec's AutoProber (2026), which lets an AI agent map a board and probe the points a person approves, but neither publishes how many board faults it catches or misses. Commercial flying probers are standard for small orders, by all-about-industries' account.
Built with what exists
the pcb-prober or AutoProber software; a 3D printer or small gantry running Marlin firmware; pogo-pin probes; a USB multimeter or a Raspberry Pi with a measuring board; kicad-testpoints to export probe positions; boards unpowered throughout.
First step
Choose the board, export its probe list and plan which faults go on which copy.
Done looks like
20 copies of one open board carrying 100 planted faults, such as missing resistors, swapped values, solder bridges and lifted pins, with the share found, the false-fail rate and minutes per board published, and a second person rerunning five of the boards.