midnight-cq:compact-testing

To unit test Compact contracts deterministically, structure tests across four layers—production source, witnesses, mocks, and simulators—using Vitest and the OpenZeppelin-compact contracts-simulator for automatic ledger and context handling.

The standard mock pattern for Compact contract testing involves configuring contractFactory, private state, and ledger access to create deployable wrappers around the modules under test within the simulator framework.

You manage witnesses in Compact contract testing by overriding them within the simulator workflow to simulate different private states and scenarios, ensuring deterministic and reproducible test outcomes across layers.

Yes, the OpenZeppelin-compact contracts-simulator integrates with Vitest to drive pure and impure circuits, automatically handling ledger and context management for deterministic Compact contract testing.

The best way to structure Compact contract tests is a 4-layer layout: production source, witnesses, mocks, and simulators, which isolates modules under test and guarantees deterministic reproducible behavior.

Compact contract tests lack reproducibility when witness states and ledger contexts are not properly mocked or overridden, which this simulator-driven framework resolves by enforcing a standard mock pattern and deterministic workflow.