pipecircuit-visualization 0.0.11

Code-derived architectural visualizations for Pipecircuit programs
Documentation
// In consuming projects, keep this expectation in behavior.rs beside architecture.rs.

use expect_test::expect;

use super::{BehaviorError, BehaviorInventory};

#[test]
fn behavior_remains_reviewable() -> Result<(), BehaviorError> {
    expect![[r#"
        - Absent or malformed snapshot scopes are refused
        - An ignored inventory fixture [ignored]
        - Benchmark functions are not behavior checks
        - Compiled discovery includes generated checks and preserves ignored status
        - Configured runner failures preserve the executable and output
        - Configured runners preserve scope filters and ignored checks
        - Configured runners refuse missing or malformed snapshot scopes
        - Equal sentences retain their distinct code locations
        - Listing order does not change the inventory
        - Macro generated checks remain discoverable
        - Malformed duplicate or inconsistent listings are refused
        - Process discovery failures retain their original details
        - Rendering is deterministic and keeps ignored checks visible
        - Snapshot scoping respects module boundaries and excludes its own module
    "#]]
    .assert_eq(&BehaviorInventory::for_snapshot(module_path!())?.render());
    Ok(())
}