Verification without hands.
WHAT TO TEST ON A DEVELOPMENT MACHINE
Logic, with hardware abstracted Protocol encoding and decoding State machines Configuration handling
WHY THAT IS POSSIBLE
Abstraction separates logic from hardware.
WHAT TO TEST ON HARDWARE
Peripheral drivers Timing Power consumption Radio behaviour
WHAT TO AUTOMATE IN A PIPELINE
Building for every target Running logic tests Static analysis Flashing and running on a device Measuring size against the available space
WHY SIZE SPECIFICALLY
Firmware exceeding storage fails at the worst moment, and growth is gradual.
WHAT TO TEST DELIBERATELY
Power loss at many points Corrupted messages Out-of-range configuration Storage full Network unavailable for long periods
WHAT TO MEASURE IN TESTING
Current consumption per operation.
WHY
It is the only way to verify battery predictions.
WHAT TO RUN CONTINUOUSLY
A long-duration test, on real hardware, always running the latest firmware.
WHAT IT CATCHES
Leaks, drift and rare faults.
WHAT TO NEVER SKIP
Testing the update path itself.
