[Smart Contracts] Run Soroban contract tests as a required CI quality gate

[ayomideadeniran]

🚀 Feature Overview

Extend contract CI beyond formatting, linting, and compilation so behavioral regressions are caught before merge.

🛠️ Implementation Requirements

• Add a dedicated contract test step to the primary CI workflow.
• Run the workspace test suite with the required Soroban or Rust test features.
• Configure deterministic environment settings and clear failure output.
• Cache dependencies without allowing cache failures to mask test failures.
• Document the local command contributors should run before opening a pull request.

🔧 Technical Specifications

Rust, Cargo, Soroban SDK, GitHub Actions.

✅ Acceptance Criteria

• Contract test failures fail the pull-request workflow.
• The command runs successfully on a clean GitHub-hosted runner.
• Existing contract build, formatting, and Clippy checks remain intact.
• CI logs identify the failing package and test.
• Contribution documentation contains the matching local verification command.

🎓 Difficulty Level

Intermediate — requires Rust and GitHub Actions familiarity.

⏱️ Timeline

ETA: 2 days

[Devadakene]

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

I am skilled enough to work on this issue having worked on something similar in the past. please assign

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

[Horlarmmy]

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

Hi, I'd like to work on this

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

[drips-wave]

Congratulations, @Horlarmmy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Horlarmmy: 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 marked as completed by a Drips Wave moderator for @Horlarmmy as part of the Stellar Wave Program's 7th Wave 🥳

Moderator's reason: [Auto-assessed] The PR was merged into the repository, effectively fulfilling all the issue requirements including the addition of the CI test step and updating the contributor documentation. The merge at 2026-08-03T22:18:33Z serves as the definitive signal of acceptance.

😎 @Horlarmmy: You earned 150 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.