Why this decision matters
Device testing fixes hardware, system, model and input conditions, then validates functions, end-to-end performance, resources, recovery, endurance, upgrade and rollback.
Run tests on the target device or a documented equivalent and retain reproducible versions and environments; workstation model results are not device-side evidence.
Conditions to confirm before development
- Record board, peripherals, system image, drivers, runtime and model versions
- Measure end-to-end latency and throughput from sensor input to business output
- Monitor CPU, accelerator, memory, storage, power and temperature
- Test power loss, network loss, abnormal input, endurance, upgrade and rollback
Implementation and delivery approach
Establish a stable baseline, then test function, performance, resources, exceptions and endurance separately. Regress affected areas after every software, model or hardware change.
Record device ID, versions, input data, environment, duration, expected and actual results, logs and issue identifiers.
Acceptance boundary
Prototype or bare-board testing proves only those conditions. Final enclosure, cooling, power, cabling and field interference require system-level retesting.