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
refs: #10388closes: #10577
doesn't close until
- exercise all the code in the contract (analytic; best effort)
## Description / Testing Considerations
- [x] test all the sequences in the product spec
- [x] enumerate all the sequences in the product spec
- [x] fix advancer/settler amount agreement bug
postponed:
-
- #10510
- [todo] C12 - Contract MUST only pay back the Pool only if they started the advance before USDC is minted
- #10554
some `test.todo()`s are out of scope of contract flow tests. Some are more feasible as exo tests:
- [todo] C18 - forward - MUST log and alert these incidents
- [skip] LP borrow - TODO: move to exo test
- [skip] LP repay - TODO: move to exo test
an some are after M1:
- [todo] PERF: Target: settlement completes in a few minutes (after USDC is minted)
- [todo] fee levels MUST be visible to external parties - i.e., written to public storage
- [todo] C21 - Contract MUST log / timestamp each step in the transaction flow
### Security / Scaling / Upgrade Considerations
n/a
### Documentation Considerations
Internal design docs are assumed background knowledge.
What is the Problem Being Solved?
The FUC contract needs a test of its flows and error handling.
This issue is short of integrating with SwingSet, vstorage or other chains.
Description of the Design / Test Plan
Package test exercising
Security Considerations
Scaling Considerations
Upgrade Considerations
The text was updated successfully, but these errors were encountered: