Sui Move Testing

Test the invariant and threat surface, not only the happy-path function name.

Target repository instructions, accepted design records, pinned toolchain behavior, and published compatibility commitments take precedence over this standard's examples.

Build the risk matrix

1. Inventory every changed behavior, invariant, public or entry path, asset, authority, lifecycle edge, event, dependency, and upgrade seam. The inventory is complete when every production change has a test owner.
2. Mark each risk layer below applicable or inapplicable for every inventoried behavior, with a reason for each inapplicable layer.
3. Read every matching specialized reference, then map each applicable risk to a direct test, property, structural check, integration check, or release gate.
4. Run the release gates below and use the final completion gate to report the result.

Cover every risk layer