Write a Firmware Regression Card

Write a Firmware Regression Card

simulation
prototyping
firmware
testing
TipHow to Use: Write a Firmware Regression Card

Pick one prototype bug that was fixed recently. Before calling the fix complete, write a small card another reviewer could rerun without you in the room.

  • Symptom: state the failed behavior, setup, firmware version, and whether it was deterministic.
  • Boundary: choose host harness, simulator, bench board, integration rig, or field observation, and explain why that boundary is faithful enough.
  • Normal case: name the input or condition that should still pass after the fix.
  • Fault case: name the realistic failure that caused the bug or could make it return.
  • Artifact: record the command, log, capture, screenshot, wiring note, or issue link that proves the result.
  • Rerun condition: name the code, dependency, hardware, OTA, configuration, or environment change that must repeat this card.

Accept the card only when the expected result, observed result, artifact, owner, and rerun condition are all explicit. Revise it if the record depends on memory or a one-off demo setup.

Back to the chapter