Setup Rust CI tests for Smart Contracts

[meshackyaro]

Description

This issue aims to address the implementation of Setup Rust CI tests for Smart Contracts.

The core objective is to: Configure Github actions to run generic Cargo tests on PRs targeting contracts DIR.

By completing this feature, we will ensure that the TrustFlow protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the Smart Contracts architecture and adherence to the existing project conventions.

When picking up this issue, please ensure you document any new dependencies or architectural decisions made during development.

Component

Smart Contracts

Difficulty

🟡 Medium

Tasks

• Review Soroban architecture and soroban-cli usage
• Implement Rust logic for: Setup Rust CI tests for Smart Contracts
• Write comprehensive unit tests in Rust
• Ensure proper event emission for indexing
• Run cargo fmt and cargo clippy
• Verify soroban contract build successfully compiles to WASM without bloating size

Acceptance Criteria

• Feature accurately implements the objective: Configure Github actions to run generic Cargo tests on PRs targeting contracts DIR.
• Any PR that introduces TypeScript/Rust errors is automatically blocked
• CI pipeline runs in under 3 minutes per PR
• Code is properly reviewed and approved by codeowners

Estimated Time

4-8 hours

[gerani1]

i would like to work on this issue given my ecperience writing rust ci tests and making sure they all pass, haven taken a look at the isssue i would be able to get it done in 3hrs

[meshackyaro]

i would like to work on this issue given my ecperience writing rust ci tests and making sure they all pass, haven taken a look at the isssue i would be able to get it done in 3hrs

Give me a walk through on how you intend to work on this issue

[gerani1]

Review the repository structure
Identify the contracts/ directory and existing Soroban smart contracts.
Check how contracts are currently built and tested (cargo test, soroban contract build, etc.).
Create a GitHub Actions workflow
Add a workflow file such as .github/workflows/contracts-ci.yml.
Configure it to trigger on:
Pull requests targeting the main branch.
Changes inside the contracts/** directory.
Set up the Rust environment
Install the required Rust toolchain.
Cache Cargo dependencies for faster CI runs.
Install any required Soroban tooling if the project depends on it.
Run quality checks

Execute:

cargo fmt --check
cargo clippy -- -D warnings
This ensures formatting and linting errors automatically fail the PR.
Run smart contract tests

Execute:

cargo test
Ensure all Rust unit and integration tests pass.
Verify contract compilation

Build the contracts to WASM:

soroban contract build

or the project's existing build command.

Confirm there are no compilation errors and no unexpected WASM size increases.
Keep CI under 3 minutes
Use dependency caching.
Avoid redundant build steps.
Run checks only when files in contracts/ change.
Document changes
In the PR, note:
Any GitHub Actions dependencies added.
Why specific CI steps were chosen.
Any architectural decisions related to contract testing.

Estimated Time: 2–4 hours depending on the current repository setup and whether Soroban tooling is already configured.

[meshackyaro]

Review the repository structure
Identify the contracts/ directory and existing Soroban smart contracts.
Check how contracts are currently built and tested (cargo test, soroban contract build, etc.).
Create a GitHub Actions workflow
Add a workflow file such as .github/workflows/contracts-ci.yml.
Configure it to trigger on:
Pull requests targeting the main branch.
Changes inside the contracts/** directory.
Set up the Rust environment
Install the required Rust toolchain.
Cache Cargo dependencies for faster CI runs.
Install any required Soroban tooling if the project depends on it.
Run quality checks

Execute:

cargo fmt --check
cargo clippy -- -D warnings
This ensures formatting and linting errors automatically fail the PR.
Run smart contract tests

Execute:

cargo test
Ensure all Rust unit and integration tests pass.
Verify contract compilation

Build the contracts to WASM:

soroban contract build

or the project's existing build command.

Confirm there are no compilation errors and no unexpected WASM size increases.
Keep CI under 3 minutes
Use dependency caching.
Avoid redundant build steps.
Run checks only when files in contracts/ change.
Document changes
In the PR, note:
Any GitHub Actions dependencies added.
Why specific CI steps were chosen.
Any architectural decisions related to contract testing.

Estimated Time: 2–4 hours depending on the current repository setup and whether Soroban tooling is already configured.

Good one!

When assigned, please ensure this and the existing CI checks are all passing

[grantfox-oss]

🦊 GrantFox — @gerani1 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #25)
2. Your PR will be reviewed by the trustflow-protocol maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@gerani1's PR #32 was approved and merged by @meshackyaro.

🏆 @gerani1: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @gerani1! Keep contributing to trustflow-protocol.