[TESTING] Write Integration Test Suite for End-to-End Invoice Financing Lifecycle

[chizzy192]

[TESTING] Issue

Metadata

Field	Value
Domain	Testing
Difficulty	Easy (2 Days)
Effort Estimate	effort: 3h
Priority	P2-Medium
Labels	good first issue
Target Branch	dev
Depends On	None

🎯 Context & Goal

Comprehensive test coverage is mandatory for smart contract security.

This issue adds tests in contracts/invoice-escrow within integration_test.rs to validate behavior under edge cases and unexpected inputs.

Ensuring robust test coverage prevents regression bugs during contract upgrades.

📂 Target Files

• contracts/invoice-escrow/src/integration_test.rs → test_runner

📋 Implementation Tasks

• Task 1: Write test functions in contracts/invoice-escrow/src/integration_test.rs.
• Task 2: Assert proper error code emissions on failure paths.
• Task 3: Verify state storage persistence after execution.
• Task 4: Ensure all workspace tests pass with cargo test --all.

🛠️ Technical Guidance

#[test]
fn test_contract_scenario() {
    let env = Env::default();
    // Test logic here
}

🔗 References & Related

• Test file: contracts/invoice-escrow/src/integration_test.rs

⏳ Delivery Window

This issue should be completed within 2 day(s) of assignment.

Contribution Workflow

1. Branch off dev: git checkout -b feature/issue-implementation dev
2. Implement all tasks in the checklist above.
3. Run all CI checks locally (see DEVELOPMENT.md).
4. Open a Pull Request targeting dev.
5. Link this issue in your PR description.

✅ Acceptance Criteria

• All implementation tasks above are completed cleanly.
• Code compiles without warnings or errors.
• All existing tests continue to pass.
• New unit tests cover all modified code paths.
• PR strictly targets the dev branch.
• Code follows project style guidelines (cargo fmt and cargo clippy).

[canicefavour]

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

I can strengthen the invoice-escrow contract by adding integration tests that cover edge cases, failure paths, and state persistence, verifying expected error codes and ensuring the full workspace continues to pass with cargo test --all, cargo fmt, and cargo clippy to prevent regressions.

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

[drips-wave]

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

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