Trying it produces confidence. Testing it produces evidence.

Technical illustration of an electronic unit under functional test with instrumentation and recorded measurements
Functional test bench

Overview

Evidence, not reassurance

There is a meaningful difference between a product that has been tried and one that has been tested. Trying it produces confidence; testing it produces recorded results against defined expectations, repeatable by someone else.

We define what has to be proven, build the test sequence and fixtures needed to prove it, run it on real assembled units and record the outcome — including the results that were not what we hoped for.

The same work usually produces the production test strategy, because the tests that prove a design is right are closely related to the tests that prove a build is correct.

Testing scope

What product testing covers

Different questions need different tests. Running the wrong one carefully still proves nothing.

01

Functional testing

Structured verification that each function behaves as specified across the intended operating range, not just at nominal conditions.

02

Performance measurement

Accuracy, timing, throughput, power draw and other measurable characteristics compared against the requirement.

03

Stress and margin testing

Behaviour at the edges of supply, temperature, load and input range, to find where margin actually ends.

04

Reliability exercises

Extended operation, power cycling and repeated-use testing to expose failures that a short test never reaches.

05

Test fixtures

Fixtures and harnesses that make a test repeatable by anyone, which is what turns a result into evidence.

06

Production test strategy

A test sequence sized for build volume and cycle time, covering the faults that actually occur in manufacture.

Test process

How a test programme is built

Defined before the units exist, so the design can support being tested.

  1. Define what must be proven

    Requirements turned into testable statements with pass criteria that are measurable rather than subjective.

  2. Test design

    Sequence, conditions, instrumentation and sample size chosen to answer each statement.

  3. Fixture development

    Fixtures, harnesses and test software built so the test can be run consistently and repeatedly.

  4. Execution

    Tests run on real units with conditions and results recorded as they happen.

  5. Analysis

    Results compared against criteria, failures investigated to root cause rather than retested until they pass.

  6. Reporting and feedback

    Documented outcomes, with findings fed back into design or production as appropriate.

Applications

When product testing is worth formalising

Any time a failure in the field is more expensive than the test that would have caught it.

Functional testMargin testingPower cyclingTest fixturesTest softwareResult recording
Application 01
Pre-production units before committing to volume
Application 02
Products entering a more demanding environment than before
Application 03
Designs with a history of intermittent field failures
Application 04
Products needing consistent test coverage at manufacture
Application 05
Units where accuracy or timing must be demonstrated per build
Application 06
Design changes that need verification before release

FAQ

Product testing questions

How testing is usually scoped and where it pays off.

Ask our team

Next step

Ready to move this forward?

Tell us what the product has to do and we will tell you what engineering it needs.