test: add comprehensive tests for contract version and capability discovery

[greatest0fallt1me]

Description:

Write comprehensive test cases for version and capability discovery.

Requirements and Context:

• Must achieve minimum 95% test coverage
• Should test version() returns non-empty and expected format
• Should test capabilities() if present (list matches implemented features)
• Should test no state change and low gas
• Should test after upgrade (if applicable) version/capabilities update

Suggested Execution:

1. Fork the repo and create a branch

   git checkout -b test/version-capability-discovery-tests

2. Implement changes

   • Write tests: src/test.rs (version and capability tests)
   • Validate test coverage

3. Test and commit

   • Run tests with coverage; include test output

Example Commit Message:

test: add comprehensive tests for contract version and capability discovery

Guidelines:

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 24 hours

[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

[MavDavis]

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

Hi, I’d like to take this on because I’ve been working with smart contracts and testing frameworks like Solidity, Hardhat, and Foundry, so writing reliable contract tests is something I’m comfortable with. I’ve built and tested upgradeable contracts before, which helps when validating things like versioning, capabilities, and post-upgrade behavior. I can ensure the tests are thorough, well-structured, and meet the 95% coverage requirement for Predictify.

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

[drips-wave]

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

🧑‍💻 @MavDavis: 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 🌊