You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Contract] Add comprehensive unit tests for escrow state machine #1
The Soroban contract has no unit tests. Every public function — `create_escrow`, `start_work`, `submit_milestone`, `approve_milestone`, `reject_milestone`, `dispute_milestone`, and all refund paths — needs at least one happy-path and one error-path test.
What needs to be done
Set up `soroban_sdk::testutils` environment in `contracts/secureflow/src/tests/`
Code review confirms the urgency: the contract currently has 0#[test] functions despite moving funds. Use the existing .config/nextest.toml (cargo nextest run). Cover the full lifecycle: create, milestone submit/approve/reject/resubmit, disputes, refunds (normal/emergency/overdue), arbiter award & refund, ratings, admin. Top audit/grant blocker.
Activity
Gbangbolaoluwagbemiga commentedon Jun 17, 2026
Code review confirms the urgency: the contract currently has 0
#[test]functions despite moving funds. Use the existing.config/nextest.toml(cargo nextest run). Cover the full lifecycle: create, milestone submit/approve/reject/resubmit, disputes, refunds (normal/emergency/overdue), arbiter award & refund, ratings, admin. Top audit/grant blocker.