Hardware-Software Integration Test Plan Template

A minimum of 5 units from the same manufacturing batch, plus 1-2 units from a different batch to catch manufacturing variability. For environmental testing, you need units you are willing to stress to failure. Ideally, keep a dedicated "golden unit" that is never subjected to destructive tests and serves as the reference baseline for all other testing. If budget is tight, use the [RICE framework](/frameworks/rice-framework) to prioritize which tests need dedicated hardware.

Automate the firmware-cloud and cloud-app interface tests. These can run in CI on every firmware build using device simulators or test harnesses. Hardware-firmware tests that require physical instruments (oscilloscope measurements, reference sensor comparisons) will remain manual or semi-automated with test fixtures. The 72-hour soak test is automated (scripted) but requires physical devices. Prioritize automating the tests you run most frequently.

Use controlled failure injection. Simulate power loss with a relay-controlled power supply, not by yanking the battery. Simulate Wi-Fi outage by blocking the MAC address on the test router, not by unplugging the access point (which affects other test stations). Simulate sensor failure by disconnecting the sensor ribbon cable at a test connector, not by cutting wires. Build test fixtures with quick-disconnect points for every interface you need to interrupt.

Start writing the test plan when hardware design is finalized (before prototypes arrive). Begin bench integration testing as soon as the first functional prototype is available with alpha firmware. System-level integration testing starts when firmware is feature-complete. Do not wait for firmware to be "stable" before starting integration testing. Integration testing is how you find the bugs that make it stable. The [guides on building a product roadmap](/guides/how-to-build-a-product-roadmap) cover how to schedule hardware and firmware milestones in parallel.

Instrument the interface. Connect a logic analyzer or oscilloscope to the bus (I2C, SPI, UART) and capture the raw signals during the failure. The waveform tells you whether the hardware is sending the correct signal and the firmware is misinterpreting it, or vice versa. Without instrumentation, integration bugs become opinion battles. With a logic analyzer trace, the root cause is visible. ---