TESTING_GUIDE.md's 'Test Categories' section documents runnable filter commands such as cargo test test_active_to_completed, cargo test test_active_to_failed, cargo test test_completed_cannot, cargo test test_failed_cannot, cargo test test_cancelled_cannot, and cargo test test_vault_creation. Grepping the current test suite shows no test function anywhere starts with any of these exact prefixes (the real names are things like test_release_funds_after_validation, test_cancel_vault_when_completed_fails, and test_create_vault_increments_id). Running any of these documented commands verbatim would silently execute zero tests and report success, which is a particularly quiet form of stale documentation since cargo test <no-match> doesn't error — a contributor following this guide could believe they ran a whole category of tests when nothing ran at all. Update these filter examples to match real, current test name prefixes.
TESTING_GUIDE.md's 'Test Categories' section documents runnable filter commands such as
cargo test test_active_to_completed,cargo test test_active_to_failed,cargo test test_completed_cannot,cargo test test_failed_cannot,cargo test test_cancelled_cannot, andcargo test test_vault_creation. Grepping the current test suite shows no test function anywhere starts with any of these exact prefixes (the real names are things like test_release_funds_after_validation, test_cancel_vault_when_completed_fails, and test_create_vault_increments_id). Running any of these documented commands verbatim would silently execute zero tests and report success, which is a particularly quiet form of stale documentation sincecargo test <no-match>doesn't error — a contributor following this guide could believe they ran a whole category of tests when nothing ran at all. Update these filter examples to match real, current test name prefixes.