Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Why this matters
remittance_nft/src/lib.rs:605-628 update_metadata_uri performs auth, URI validation, legacy-score migration (get_or_migrate_metadata), persistence, and a UriUpd event emit, but no test in remittance_nft/src/test.rs invokes it. The success path, the NftNotFound path (no NFT), unauthorized-minter rejection, and the legacy-migration path are all uncovered.
Acceptance criteria
Files to touch
contracts/remittance_nft/src/test.rs
Out of scope
- Changing update_metadata_uri behavior
Why this matters
remittance_nft/src/lib.rs:605-628 update_metadata_uri performs auth, URI validation, legacy-score migration (get_or_migrate_metadata), persistence, and a UriUpd event emit, but no test in remittance_nft/src/test.rs invokes it. The success path, the NftNotFound path (no NFT), unauthorized-minter rejection, and the legacy-migration path are all uncovered.
Acceptance criteria
Files to touch
contracts/remittance_nft/src/test.rsOut of scope