Skip to main content
FixturFab

Testing from Prototype to Production

How testing requirements evolve across the product lifecycle. Plan your fixture progression and test strategy as you scale from prototype to production.

Testing requirements change at each stage of product development. A prototype needs debug and design validation. A pilot run needs repeatable pass/fail testing. Production needs throughput, yield tracking, and fixtures that operators can run without engineering support.

The testing lifecycle breaks into four stages, each with different volumes, constraints, and fixture needs:

  • Prototype (1-25 units): Design validation. Fixtures usually premature.
  • Pilot/NPI (25-500 units): Process validation. Fixture investment often begins here.
  • Low volume (500-5,000 units): Process establishment. Production-grade fixtures required.
  • Production (5,000+ units): Throughput and yield. Durability and automation matter.

The common mistake is treating each stage as independent. Decisions made during prototype and NPI -- test point placement, fixture vendor selection, test strategy -- constrain what's possible at production. Planning ahead doesn't mean spending more early. It means making choices that leave good options open later.

Prototype stage: design validation#

At prototype, you're answering one question: does the design work?

Volume is low -- 1-25 units. The design is still changing. Engineers are debugging the board, not running production tests. Time pressure varies, but the focus is exploratory: oscilloscope probing at key nodes, bench power-up and bring-up, manual functional verification.

What NOT to do at prototype#

  • Invest in production fixtures. The design will change, and you'll pay for fixtures that don't match the next board revision.
  • Write exhaustive test procedures. It's too early. Focus on understanding the design, not documenting a test process.
  • Optimize for cycle time. Volume doesn't justify it.

Fixture considerations#

For most prototype situations, fixtures are premature. Possible exceptions:

  • Very high pin count boards requiring simultaneous probing
  • Safety-critical applications requiring comprehensive test from day one
  • Board design carried over from an existing product (known to be stable)

If a fixture is needed at prototype, use the simplest approach that achieves your immediate goal. A Dev fixture provides reliable probing without production-level investment -- and at 2-3 weeks delivery, it won't hold up your prototype schedule.

Pilot/NPI stage: process validation#

New Product Introduction bridges engineering and manufacturing. You're validating that the design can be built and tested repeatably.

Volume climbs to 25-500 units. The design should be approaching freeze. Time pressure is typically high because production launch is coming. Testing serves two purposes: verify each unit works, and validate the test process itself.

This means documented test procedures that others can execute, pass/fail criteria that don't depend on an engineer's judgment, repeatable results across operators and shifts, and data logging for trend analysis. If your test produces different results depending on who runs it, you have a process problem -- and that problem will get worse at higher volume.

Why most teams need help here#

Here's the reality most NPI guides skip:

Professional fixtures typically require mechanical engineering expertise that EE-focused teams don't have in-house. The build-vs-buy math tilts toward outsourcing once you account for engineering time, iteration cycles, and the opportunity cost of delayed testing. Our build vs. buy guide walks through the full comparison.

With current options, custom fixtures can arrive in 2-3 weeks -- fast enough to fit within most NPI timelines. That changes the calculation from "can we afford to outsource?" to "can we afford not to?"

Common NPI mistakes#

These mistakes compound at scale

NPI is the last chance to fix process issues cheaply. Every problem you carry into production becomes harder and more expensive to resolve.

Mistake 1: No test procedure documentation. Engineers test successfully; production operators can't replicate results. The engineer knew which probes to wiggle and which test sequence mattered. The operator doesn't.

Mistake 2: Prototype fixture for pilot volumes. That hand-wired fixture that worked for 10 units fails at 200. Probes wear, alignment drifts, and intermittent contact creates false failures that erode trust in the test process. If you're still running a prototype fixture for pilot volumes, you're building problems into your baseline.

Mistake 3: Ignoring test data. Running tests without analyzing results means you'll repeat the same problems at production volume. NPI is when you establish the yield baseline that drives process improvement later.

Low volume production: process establishment#

Low volume production bridges NPI and full-scale manufacturing. Volume reaches 500-5,000 units, the design is frozen, and the schedule is production-driven rather than engineering-driven.

Testing must be production-ready at this stage. Operators follow documented procedures. Tests run at consistent cycle times. Failures are logged and analyzed. Yield data drives process improvement. You need infrastructure that supports this: production-grade test fixtures, test equipment matched to your volume, training materials for operators, and a failure analysis workflow.

Fixture considerations#

Low volume production requires fixtures that deliver repeatable cycle times, operator-level simplicity, enough durability for the expected volume, and clear fault isolation when tests fail.

Dev Pro fixtures handle many low-volume applications well. Built with G10 or carbon fiber construction, they're rated for approximately 10,000 test cycles and support exchangeable cartridges -- meaning you can swap board designs without buying a new fixture base. For higher throughput requirements or automation compatibility, Production fixtures may be justified.

Planning for scale#

Even at low volume, plan for what happens if the product succeeds:

  • Will current fixtures handle increased volume? A Dev Pro fixture rated for 10,000 cycles covers 5,000 units with margin. Beyond that, you'll need to plan a transition.
  • What's the lead time for production fixtures? Dev and Dev Pro fixtures deliver in 2-3 weeks. Production fixtures typically take 6-8 weeks from most vendors. Don't wait until you need production fixtures to start ordering them.
  • Where are the process bottlenecks that scaling will expose? Fixture cycle time, operator handling, and test equipment throughput are the usual suspects.

Order production fixtures before your volume demands them. A 6-8 week lead time means you should start the process when you're at 60-70% of your current fixture's rated cycle life -- not when probes are already wearing out.

Fixture vendors can often design production-ready fixtures that initially run in manual mode, then integrate with automation as volume grows. Planning this upgrade path during low volume avoids redesigning the fixture from scratch later.

Production stage: manufacturing scale#

At production volume -- 5,000+ units annually -- testing is about throughput, yield, and cost per unit. The design is frozen. Changes are expensive. The line must run.

Production testing optimizes for cycle time (seconds matter at volume), first-pass yield (directly affects unit cost), fault coverage (catch defects before they ship), and data (trends enable continuous improvement). A typical production test configuration combines AOI for post-assembly visual inspection, ICT for component verification, functional test for system validation, and boundary scan for complex boards that require it.

Fixture considerations#

Production fixtures must withstand continuous use -- hundreds of thousands of cycles with minimal maintenance. They need fast insertion and removal for operators running hundreds of boards per shift, and they need to be automation-compatible if you're integrating with test handlers.

Production fixtures are engineered for this environment. The higher upfront cost is amortized across production volume, and replica pricing reduces the cost of subsequent orders once your fixture design is in the system.

Contract manufacturer deployment#

Many production fixtures go to contract manufacturers. This adds requirements beyond what internal testing demands:

  • CM acceptance standards. Your CM expects a professional tool, not a prototype. As one customer described it: "There's no taping stuff to a piece of plywood and explaining it."
  • Test equipment compatibility. Verify your fixture works with the CM's test infrastructure before shipping it overseas.
  • Documentation and training. Operators at the CM site need to run the test without calling your engineers. Complete documentation isn't optional.
  • Maintenance and calibration support. Plan for probe replacement and alignment checks over the fixture's production lifetime.

CM readiness checklist

Before shipping a fixture to your contract manufacturer: verify test equipment compatibility, prepare operator documentation with photos, include a maintenance schedule with spare probes, and validate the fixture against known-good boards at your site first.

Professional fixtures with complete documentation smooth CM deployment. If you're scaling to production across multiple sites, consistent fixtures at each location simplify quality management.

Fixture progression by lifecycle stage#

Fixture tier selection maps to lifecycle requirements. The table below shows the typical progression:

Lifecycle StageVolumeRecommended FixtureRationale
Prototype< 25None / DevDesign changing; minimal investment
Pilot/NPI25-500Dev / Dev ProNeed repeatability; design stabilizing
Low Volume500-5,000Dev Pro / ProductionProcess established; durability matters
Production5,000+ProductionThroughput and durability critical

Upgrade path#

Planning ahead enables smooth transitions between fixture tiers:

  1. Design fixtures for the interface. Use consistent mounting and connections across fixture tiers so test programs transfer between fixture generations.
  2. Preserve test coverage. Test programs written for a Dev Pro fixture should run on a Production fixture with the same probe configuration.
  3. Plan lead times. Dev and Dev Pro fixtures deliver in 2-3 weeks. Production fixtures take 6-8 weeks from most vendors. Order production fixtures before your volume requires them -- not when you're already behind.
  4. Use replica pricing. Once a fixture design is in a vendor's system, subsequent orders of the same configuration eliminate NRE costs. Ordering your second or third fixture is faster and cheaper than the first.

Decisions that compound#

Certain decisions early in the lifecycle constrain what's possible later. Getting these right doesn't cost more -- it costs attention at the right moment.

Design for test#

Test points included during PCB layout enable bed-of-nails fixture testing. Test points omitted during layout require expensive board respins or permanently reduced test coverage.

When to decide: During PCB layout. Once the design goes to fabrication, your test access is locked in.

Cost of delay: A board respin to add test points costs $5,000-$20,000 and adds 4-8 weeks. Skipping test points entirely means reduced fault coverage for the product's entire production lifetime.

Test points are the single highest-leverage decision for your testing future. Including them during your current layout cycle costs nothing. Omitting them locks in reduced fault coverage for the product's entire production lifetime.

What to do now: Allocate test points during your current layout cycle. Even if you don't plan to use fixtures at prototype, you'll want them at NPI. See our design for test guide for specific guidelines on test point size, spacing, and placement.

Test strategy#

The testing methods you choose at NPI tend to carry through production. Changing test strategy mid-production is disruptive and expensive -- new fixtures, new test programs, retrained operators, and a period of uncertain yield data while the new process stabilizes.

When to decide: During NPI planning, before you invest in fixtures and test software for a specific approach.

Cost of delay: Switching from functional-only testing to ICT during a production ramp means a new fixture, new test development, and weeks of parallel testing to validate the transition. Teams that plan for ICT from NPI avoid this disruption entirely.

What to do now: Define your test strategy before NPI. Decide which tests happen at which stage, which defects each test catches, and how test data flows into your quality system. For a broader view of testing approaches, see how to test circuit boards at scale. Embedded systems teams navigating this progression have unique constraints -- see embedded systems testing solutions for how we support that path.

Fixture vendor relationship#

Choosing a fixture vendor is choosing a partner for the product's production lifetime. Switching vendors mid-production means re-qualifying fixtures, transferring design knowledge, and risking timeline disruption during the transition.

When to decide: Before ordering your first production-intent fixture. NPI is the natural evaluation window.

Cost of delay: Vendor switching after production starts introduces 6-12 weeks of transition risk. If your current vendor can't support production volume or design revisions, you'll discover this at the worst possible time.

Evaluate vendors on lifecycle fit, not just price. Can they support your full volume range from NPI through production? How do they handle design revisions -- is it a new project each time, or does the existing design carry forward? What's their delivery track record? These questions matter more than the first fixture quote.

Our evaluating fixture vendors guide provides a detailed vendor selection framework covering capability, delivery, and long-term support.

What this looks like in practice#

A typical hardware company progression:

Prototype (Month 1-3):

  • 10 boards hand-built
  • Engineer bench testing
  • Many design revisions
  • No fixture investment

Pilot (Month 4-6):

  • 100 units from CM
  • Dev Pro fixture for ICT -- ordered in month 3, delivered in 2-3 weeks, ready before first pilot build
  • Test procedure documented
  • First yield data collected

Low Volume (Month 7-12):

  • 2,000 units shipped
  • Same Dev Pro fixture still working (rated for 10,000 cycles)
  • Test process refined based on yield data
  • Production fixture ordered in month 10, allowing 6-8 weeks before volume ramp

Production (Month 13+):

  • 1,000 units/month
  • Production fixture deployed at CM
  • Automated test handler integrated
  • Continuous yield improvement driven by test data

For a detailed example of this progression with real metrics, see how an IoT startup scaled from prototype to production testing.

Plan your test infrastructure now#

Testing evolves with your product. Match your approach to each stage:

  • Prototype: Debug focus, minimal fixture investment
  • NPI: Validation focus, documented procedures, appropriate fixtures
  • Low Volume: Process focus, production-ready fixtures
  • Production: Throughput focus, automated, optimized

The time to think about production testing is during design -- not when you're trying to hit production launch. Decisions about test points, test strategy, and fixture vendors compound over time. Getting them right early costs attention. Getting them wrong costs months.

Figuring out your next step?#

Where you go from here depends on where you are in the lifecycle.

If you're deciding whether to build fixtures internally or outsource, start with the decision framework:

Build vs. Buy: Test Fixtures

The full cost analysis and decision framework for fixture procurement.

If you've decided to work with a vendor and want to evaluate your options:

Evaluating Test Fixture Vendors

A detailed vendor selection framework covering capability, delivery, and support.

If you already know what you need and want to check pricing:

Configure in Studio

Explore fixture options and get instant pricing for your volume requirements.

Last updated:February 17, 2026