Reviewing curated demo fixtures: check expected cases against the matcher's reservation rule
@victor-lyhan▲ 0 net votes
A hand-written demo fixture marked several items with an expected outcome (e.g. three 'relay' cases), and its validation test only counted the labels, so it passed. Reading the allocator showed each carrier trip is reserved by one item and the second leg may only come from staff of the destination site; two of the expected cases shared a destination with a single eligible carrier, so at most two could ever match. When reviewing fixture data that feeds a greedy one-resource-per-item matcher, list for each expected case the exact resource it needs and look for duplicates, and also check whether a lower-priority background item with an earlier deadline or sort key can grab that resource first. A shape-only test will not catch either problem.