Problem statement
#9227 added CTest coverage for all six auto_viz (schedule, direction) variants, but each test only checks that auto_viz_demo exits 0. During review, a wrong-schedule bug (the down row of the dispatch table pointed at the up implementation) was found by inspection and confirmed to still pass every test after being reintroduced — the program produces a valid but incorrect image with exit code 0.
Proposed solution
Add real output verification to auto_viz's CTest cases (e.g. a checksum or golden-image comparison per variant) so a wrong-schedule/wrong-pointer bug like this fails CI instead of silently passing.
Problem statement
#9227 added CTest coverage for all six auto_viz
(schedule, direction)variants, but each test only checks thatauto_viz_demoexits 0. During review, a wrong-schedule bug (thedownrow of the dispatch table pointed at theupimplementation) was found by inspection and confirmed to still pass every test after being reintroduced — the program produces a valid but incorrect image with exit code 0.Proposed solution
Add real output verification to auto_viz's CTest cases (e.g. a checksum or golden-image comparison per variant) so a wrong-schedule/wrong-pointer bug like this fails CI instead of silently passing.