A test plan is the part of an R&D programme that most buyers under-resource and over-trust. A prototype can switch on, heat water and spray steam in a demo, and still fail three months into customer use. If your product idea is a steam cleaning machine, a mobile car-wash unit or a piece of non-standard automation equipment, the test plan is what turns "the sample works" into a product you can put a price on, a delivery date against and a warranty behind.
The plan does not need to be long. It needs to say, for every item, what is tested, under what condition, with what instrument, and what result counts as a pass. Below is the structure we use when a customer brings us an equipment project, and what each section has to answer before you commit to tooling and a first batch.
Start with the requirement sheet, not the test sheet
Every test item in a usable plan traces back to a written requirement. If a requirement is not written down, it will not be tested, and it will surface later as a complaint. Before defining any test, fix four things with your engineering partner or your own team: the usage scenario (indoor garage, outdoor parking area, production line, clinic, kitchen), the core functions versus the nice-to-have functions, the target cost band, and the annual volume you expect. That is exactly what the requirement definition and product sorting module of our product R&D accelerator for cleaning equipment produces: a requirement analysis document, a product feature list and a preliminary cost direction. The test plan is written against those documents, item by item.
1. Functional testing: prove every declared function on the real prototype
Functional testing answers one question: does each function in the feature list behave as specified on the machine you intend to copy, not on the first hand-built sample. For a cleaning machine this normally covers:
- Mode switching: dry steam, wet steam and hot water, including how the machine moves between them and what the panel shows while it does so
- Control panel and HMI behaviour, alarm indication and protection functions
- Execution mechanisms: pump start-up, gun and nozzle response, vacuum pickup, foam delivery where fitted
- Water and fluid handling: tank filling, inlet connection, water-shortage behaviour, drainage
- Power handling: charge connection, battery-powered operation, and what happens when supply runs low mid-job
Write the expected result next to each item before the machine is on the bench. A test plan with 40 items and a blank "expected" column is a shopping list, not a plan.
2. Performance testing: measure the parameters you will publish
Performance testing decides whether the machine reaches the numbers you plan to put in the datasheet and on the product page. For a high-temperature, high-pressure cleaning machine that means measuring output pressure, steam and water temperature, flow, heating power draw, suction performance and energy consumption, and then checking the cleaning result on real soil — engine grease, road film, food residue — rather than on a clean test bench. Our hardware testing service covers this under pressure, temperature and flow testing, suction and energy consumption testing, and cleaning-effect testing.
Two practical points. Measure at cold start and after continuous running, because a heating system that reaches its stated temperature cold will behave differently at hour three. And record the instrument you used with its range and resolution; a figure without a method cannot be re-checked when the same model is built by a second supplier or when a customer disputes a claim.
3. Stability testing: run it until something gives
Stability and endurance testing is where cleaning-equipment projects most often fail quietly. The plan should include continuous running under load, repeated start-stop cycles, and a deliberate attempt to reproduce every fault found earlier. Heating elements, pumps, seals, hoses, connectors and control relays each have their own failure behaviour under heat, vibration and wet duty, so define the run duration and the number of cycles up front and log temperature rise at the points that carry current or pressure.
4. Safety testing: the section you cannot negotiate away
Steam and hot water under pressure, in wet environments, on a mobile chassis, is a combination that punishes weak electrical and pressure design. Our safety test scope includes:
- Electrical safety inspection, leakage and emergency-stop testing
- Pipeline and vessel sealing checks, and high-temperature protection behaviour
- Abnormal-condition tests: no water in the tank, blocked nozzle, low supply voltage, unattended overheat
- Protection functions as built: leakage, short-circuit, high-temperature, high-voltage and water-shortage protection are listed on our machine pages — confirm with our engineers which items apply to your configuration before you publish them
Treat the safety items as pass/fail with a signed record. Anything conditional goes back into the design loop, not into the manual as a caution note.
5. Life and reliability testing: what the unit does in year two
Buyers of industrial steam cleaning equipment judge the machine over years of daily duty, so the plan should name the components most likely to wear — heating elements, pumps, seals, hoses, switches and buttons, battery pack where fitted — and set an accelerated cycle for each, with fatigue and wear observations recorded against a photograph and a part number. This is also where you decide service intervals and spare-part lists, which is information you need for pricing before the first quotation goes out.
6. A factory test plan: the last section, and the one production needs
A design that passes once is not a product. The final block of the plan defines what every unit is checked for on the way out of the factory: the test items, the order of them, the record form the operator fills in, and the qualified/unqualified threshold for each item. Writing this before your first small-batch run means the batch produces both goods and evidence. We help customers set up these factory inspection procedures and criteria as part of the testing scope, so the same checks repeat on every unit rather than on the prototype only.
What the finished plan should hand you
Read the deliverables list before you start. A completed test programme on a prototype or pre-production unit should leave you with:
- A test plan and record forms, with functional and performance reports
- A problem list with cause analysis, and retest confirmation records
- Optimization suggestions for structure, electrical control and component selection
- Factory inspection standards and a mass-production risk note
If your project is still at the idea stage and there is no prototype on the bench yet, a test plan cannot be written against nothing. That is the point of running a technical feasibility assessment and a prototype route design first: the plan for a principle prototype, an engineering prototype and a small-scale trial run are three different documents, and the R&D accelerator decides which one you are paying for.
Common gaps in an equipment test plan
- Testing the first prototype only, then assuming the design transfers to the production build without re-verification
- No abnormal-condition cases: the machine is only ever tested doing what it is supposed to do
- Performance figures taken in a workshop rather than in the target usage environment
- No acceptance threshold, so "works fine" becomes the verdict and nothing is ever closed out
- No factory test plan, leaving the first batch to be judged by whoever assembles it
Putting the plan to work
The cheapest version of a test plan is the one written before the tooling order, not after the first customer return. Send us the scenario, the functions you want and the cost band you are working to, and we will scope the test plan around your stage: an assessment of what still needs verifying, or a full programme from functional and performance testing through to factory inspection standards. If you are preparing an OEM or ODM unit, we can run that alongside product development and manufacturing automation support, so the design changes and the test evidence move together.
