Add Unit Tests for Storage Diff Logic

[Timi16]

Description

The storage diff logic in src/inspector/storage.rs lacks unit tests. Write tests covering all diff scenarios: keys added, keys removed, keys modified, and no changes.

Requirements

• Test: empty before + empty after = no diff
• Test: key added (appears in after, not in before)
• Test: key removed (appears in before, not in after)
• Test: key modified (same key, different value)
• Test: large storage with mixed changes
• Test: binary/non-UTF8 values handled without panic

Suggested Execution

1. Branch: git checkout -b test/storage-diff-unit-tests
2. Add #[cfg(test)] module to src/inspector/storage.rs
3. Write one test function per scenario
4. Run cargo test inspector to verify
5. Commit: test: add unit tests for storage diff logic

Acceptance Criteria

• All 6 scenarios covered
• Tests are isolated (no file I/O or network)
• All tests pass
• Edge cases (empty, large, binary) covered

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Samuel1505]

@Samuel1505 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Please assign me this issue, i would like to work on it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Samuel1505 to this issue.

[Amas-01]

@Amas-01 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi maintainer, I’ll appreciate you letting me take up this task as I’m a full-stack developer with a good track record.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Amas-01 to this issue.

[DioChuks]

@DioChuks has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on this issue cos i can build the storage diff logic in src/inspector/storage.rs lacks unit tests. I would write tests covering all diff scenarios: keys added, keys removed, keys modified, and no changes.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DioChuks to this issue.

[drips-wave]

Congratulations, @DioChuks! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @DioChuks: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊