====== Testing ======

MTRP testing is best done in layers. Start with direct-neighbor behavior, then verify forwarding, then verify policy behavior.

===== Basic Bring-Up =====

Expected checks:

  * node claims an address
  * hello traffic is visible
  * direct neighbors appear in the neighbor summary
  * local route advertisements appear in route summaries

===== Multi-Node Bench Test =====

With 3 or more nodes:

  * confirm each node sees direct neighbors
  * confirm learned routes appear with additive metrics
  * confirm sequence values advance normally
  * confirm direct routes are preferred over worse indirect routes

===== Forwarding Test =====

To verify actual forwarding behavior:

  - place node A and node C so they cannot communicate directly
  - keep node B between them
  - send traffic from A to C
  - confirm route resolution falls back to a forwarded candidate
  - confirm preferred-route entries appear for forwarded destinations

===== Policy Test =====

To verify routing policy behavior:

  * test ''BEST_METRIC'' with one clearly better path
  * test ''LAST_UPDATED'' by refreshing one candidate later than another
  * test ''STICKY_BEST_METRIC'' with similar metrics and controlled changes
  * test ''MOST_RELIABLE'' by intentionally degrading one neighbor link

===== Reliability Test =====

For current reliability scoring:

  * send repeated unicast traffic to a neighbor
  * introduce packet loss or weak RF conditions
  * confirm ''txSuccess'', ''txFail'', and reliability score change as expected

===== Diagnostics to Watch =====

  * summary output
  * neighbor summary
  * route summary
  * preferred route summary
  * serial event logging for hello and route advertisements