Refactor contract Tests to use property-based and invariant testing

[Smartdevs17]

Description

Contract tests are example-based missing edge cases. Refactor to property-based testing for comprehensive coverage of contract invariants.

Acceptance Criteria

• Property definitions for all critical invariants
• proptest integration with seed corpora
• State machine testing for multi-step scenarios
• Invariant test suite for fuzz testing
• CI integration with shrinking
• Test coverage report comparison

Technical Scope

• contracts/tests/invariants/
• contracts/subscription/tests/
• contracts/types/src/
• Edge: test timeout for complex properties, state explosion in state machine tests

[TUPM96]

Implemented in #441

What changed:

• Added package-level Soroban property/invariant tests for subscription flows using the real storage contract and generated clients.
• Covered plan count consistency, charge accounting, lifecycle transitions, refund bounds, and user/plan subscriber invariants.
• Updated invariant CI to run the registered property_invariants test target with CI-controlled PROPTEST_CASES / shrink settings.

Verified locally:

• cargo fmt --check
• PROPTEST_CASES=16 PROPTEST_MAX_SHRINK_ITERS=1000 cargo test -p subtrackr-subscription --test property_invariants -- --nocapture
• cargo test --workspace --lib --verbose
• git diff --check

[temi-Dee]

@temi-Dee has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hi maintainer i can work on this issue

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

[JoyAdah]

@JoyAdah has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Please assign

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

[drips-wave]

Congratulations, @JoyAdah! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[drips-wave]

This issue has been completed by @JoyAdah as part of the Stellar Wave Program's 5th Wave 🥳

😎 @JoyAdah: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.