Write contracts/docs/testing.md: how the Soroban test environment is used across the three contracts — Env::default(), address generation, mock_all_auths versus asserting real auth, advancing ledger time for expiry paths, and cross-contract test setup where proposals calls into group_treasury.
Acceptance criteria:
- Documents the standard test scaffolding with a copyable example
- Explains testing authorization properly, and the risk that blanket auth mocking hides a missing
require_auth
- Documents how to test time-dependent behaviour such as proposal expiry
- Documents the
test_snapshots/ directory: what generates it, that it is committed, and that it is Prettier-ignored as generated output
Write
contracts/docs/testing.md: how the Soroban test environment is used across the three contracts —Env::default(), address generation,mock_all_authsversus asserting real auth, advancing ledger time for expiry paths, and cross-contract test setup whereproposalscalls intogroup_treasury.Acceptance criteria:
require_authtest_snapshots/directory: what generates it, that it is committed, and that it is Prettier-ignored as generated output