Create Comprehensive Tests for Shade-led Account Restriction

[codebestia]

Description 📝

Create a test suite to verify the end-to-end integration between the central Shade contract and the Merchant Account contract during the restriction process. This confirms that roles are correctly enforced at the entry point and state changes propagate across contracts.

Proposed Steps 📝

• Test Setup:
  • Create contracts/shade/src/tests/test_shade_restriction.rs.
  • Deploy the Shade contract and register a merchant to deploy their account contract.
• Implement Test Cases:
  • Admin Command:
    • Call restrict_merchant_account(true) as the Shade Admin.
    • Verify the Merchant Account contract's is_restricted_account() now returns true.
    • Verify Shade event emission.
  • Manager Command:
    • Call restrict_merchant_account(false) as a Shade Manager.
    • Verify the Merchant Account contract status updates correctly.
  • Unauthorized Attempt:
    • Attempt to trigger restriction from a random account or the merchant themselves through the Shade contract.
    • Expect Shade-level NotAuthorized or role check panic.
  • Invalid Merchant:
    • Attempt to restrict an account for an address that is not registered as a merchant.
    • Verify appropriate error/panic (e.g., MerchantNotFound).

Acceptance Criteria ✅

• Tests confirm cross-contract state synchronization.
• Access control at the Shade level is strictly verified.
• Integration is proven to handle success and failure cases gracefully.

[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

[Anuoluwapo25]

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

Hi maintainer, I'd like to take on this issue as i'll fully implement what is requested as i'm a fullstack web3 developer with experiences.

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

[Dagdon]

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

Hello, can I work on this please?

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

[0xVida]

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

I can add end-to-end tests to validate Shade-led merchant account restriction, ensuring role enforcement and cross-contract state synchronization.

I will:
set up integration test: deploy Shade contract, register a merchant, and obtain the deployed Merchant Account contract

add test cases:
• admin restricts account → call restrict_merchant_account(true), verify is_restricted_account() returns true and event emitted
• manager toggles restriction → call restrict_merchant_account(false), verify status updates correctly
• unauthorized caller → random address or merchant attempts restriction → expect NotAuthorized / role check panic
• invalid merchant → attempt restriction for non-registered address → expect MerchantNotFound

verify cross-contract state changes and strict access control enforcement

Experience

i’ve written Soroban integration tests covering role-based access control and cross-contract state validation, so I can deliver reliable restriction tests with clear assertions and full success/failure coverage

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

[Tijesunimi004]

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

I'd like to work on this issue

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

[chigozirim007]

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

Can I work on this issue?

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

[anonfedora]

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

I'm Anonfedora, I'm a Fullstack Blockchain Engr. I'm proficient in Rust (soroban), Rust serverside with Axum and tokio, Nestjs, epxressjs have vast experience in contributing and building on the Stellar ecosystem with the Rust using soroban's SDK.
I'm also good at comprehensively testing features.
ETA: < 12 hours

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

[Ogstevyn]

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

Hi, I'd like to pick up issue #74 — writing the comprehensive test suite for Shade-led account restriction in ShadeProtocol.

I'm comfortable with the shade-stellar-contract codebase and have experience writing Soroban integration tests covering cross-contract state verification, MockAuth for role-based access control testing, and asserting both success and panic paths. I'll create test_shade_restriction.rs with all four required test cases: admin restriction, manager unrestriction, unauthorized attempt (random account + merchant self-call), and invalid merchant, verifying cross-contract state sync and correct event emission throughout.

Could you assign this to me? Happy to start immediately.

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

[ALIPHATICHYD]

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

Hi maintainer
I'd love to work on this issue

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

[drips-wave]

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

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

[Dagdon]

Hello @codebestia my apologies for delays, I will open a PR soon.