A testpoint report can contain valid coordinates for the wrong testing stage. A location accessible on a bare PCB may be covered by a component after assembly, and a fabrication testpoint assignment may not appear in an assembly test export. Define the purpose before generating the file.
Altium’s testpoint documentation distinguishes fabrication and assembly assignments and their report generators. It also notes separate settings for direct output and Output Job generation. Verify the actual export path used for the manufacturing handoff.
Define the required contact population
List the nets or signals that require access and identify the intended fixture or probe approach. Distinguish stimulus, measurement, programming, and reference contacts. A net appearing in the report does not establish that the selected contact can support the intended electrical or mechanical use.
Review the populated board state, including fitted components, coating, labels, and mechanical parts. Identify contacts that become inaccessible later in assembly and define the test stage at which they are available.
Reconcile the exported fields
| Field | Question to verify |
|---|---|
| Testpoint identity and net | Does the contact correspond to the intended signal? |
| X and Y coordinates | Are units and origin agreed with the receiver? |
| Board side | Can the fixture approach the stated surface? |
| Pad or via geometry | Is the physical contact suitable for the selected probe? |
Check bottom-side coordinates using an asymmetric set of contacts. Do not assume the receiver applies the same mirroring convention as the EDA view. Agree the coordinate interpretation with the fixture designer and retain an annotated example. Include at least three non-collinear reference contacts when checking the transform, so translation, rotation, and a possible mirror can be distinguished. Confirm the selected points are actual accessible probe targets rather than convenient graphic markers.
Verify coverage and exclusions
- Compare required nets with the exported contact set.
- Inspect duplicate contacts and their intended use.
- Review nets without an assigned accessible point.
- Check contacts close to obstructions or board edges.
- Confirm that the final report matches the released variant.
A coverage count is useful only when its denominator is defined. State whether it counts nets, selected signals, or physical contacts. Several testpoints on one net should not hide another required net with no usable access.
Close the handoff with the report, coordinate convention, board state, and unresolved access exceptions. The fixture channel-map guide addresses the next stage: connecting those intended contacts through the fixture hardware to the logical test steps.
Move from reading to a build-ready project
Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.
Open the DFM checklist