The short answer
What this setting controls
A flying-probe test uses movable probes, so it is well suited to prototypes and changing designs. A full test checks more of the netlist; a random or sample path may reduce coverage and cost less.
Choose from the available coverage after the netlist and quantity are known. Consider fixture economics, test-point access, bare-board yield, critical nets and whether assembly testing will add another layer of evidence.
Options in the order form
How the available choices differ
| Choice | Use it for | Engineering note |
|---|---|---|
| Flying-probe full test | High coverage without a dedicated fixture | Well suited to prototypes and changing designs. |
| Flying-probe random test | Quantity-eligible sampled coverage | Use only when the acceptance plan allows sampling rather than complete continuity testing. |
Compatibility
What can change with this selection
- Some choices appear only at higher quantities.
- An electrical test does not validate firmware, system behaviour or component functionality.
- If the page disables a choice, treat it as a compatibility result and adjust the controlling design decision rather than forcing the value.
Practical recommendation
How to make the decision
- Use the full flying-probe option when coverage matters and the quantity supports it.
- Use a random or sample path only when the risk and acceptance plan allow reduced coverage.
- For safety-critical or high-volume builds, document the test coverage and failure disposition.
Before release
Check these points before adding the quote to cart
- Confirm the selected value matches the released Gerber, drawing, stack-up, BOM or assembly plan.
- Review any fields that changed automatically after this selection.
- Check the board preview and server-calculated estimate before adding the quote to cart.
- Use the full flying-probe option when coverage matters and the quantity supports it.
- Use a random or sample path only when the risk and acceptance plan allow reduced coverage.
- For safety-critical or high-volume builds, document the test coverage and failure disposition.
Frequently asked questions
Answers for ordering and design review
Why is the random test hidden at small quantity?
The process economics and supported test path can depend on order quantity. The page follows the available options returned for the current build.
When should I change Electrical test?
Change it when the released electrical, mechanical, thermal, assembly or quality plan gives a measurable reason. Otherwise keep the compatible default and review the resulting board preview and estimate.
Why is an option disabled?
The current material, geometry, layer count, quantity or another selected process makes that combination unavailable. Change the controlling selection or revise the design package rather than trying to bypass the disabled state.
Can I rely on the online choice as final manufacturing approval?
No. The interface screens known combinations and requests pricing, while final manufacturability remains subject to the released files and technical review.
What should I record outside the order form?
Put controlled requirements in the fabrication drawing, assembly drawing, stack-up, BOM or acceptance plan. Use Special instructions only for a concise pointer to that controlled requirement.
Will changing this update other selections?
It can. The order form re-evaluates compatibility and may replace a now-invalid dependent choice before requesting a fresh server-side estimate. Review every highlighted or automatically changed field.
What if the design requires an option that is not offered?
Do not approximate it with a different label. Recheck the controlling material and geometry, document the actual requirement, and request technical review before placing the order.
Further reading
Standards and technical references
Use the latest applicable revision and your organisation’s controlled requirements when a standard forms part of product acceptance.