[TESTING] Add Fuzzing Target for Storage Key Symbol Collisions

[chizzy192]

[TESTING] Issue

Metadata

Field	Value
Domain	Testing
Difficulty	Medium (4 Days)
Effort Estimate	effort: 7h
Priority	P2-Medium
Labels	enhancement
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 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/test.rs → test_runner

📋 Implementation Tasks

• Task 1: Write test functions in contracts/invoice-escrow/src/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/test.rs

⏳ Delivery Window

This issue should be completed within 4 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).

[godwinnoah1]

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

Hello Maintainer, i would like to work on this issue, please assign me.

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

[nelly439]

@nelly439 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 issue.

I have experience writing comprehensive Rust/Soroban smart contract tests with a focus on edge cases, authorization, storage invariants, and regression prevention. Since this task is centered on improving the security and reliability of the invoice-escrow contract through testing, it aligns well with my experience.

My approach will be to first review the existing contract implementation and current test suite to identify uncovered execution paths and failure scenarios. I'll then expand contracts/invoice-escrow/src/test.rs with focused unit tests that validate both successful execution and expected failure conditions without modifying the contract's intended behavior.

The implementation will include:

Adding new unit tests in contracts/invoice-escrow/src/test.rs.
Verifying expected success flows and contract state transitions.
Asserting the correct contract error codes are returned for invalid operations and edge cases.
Confirming persistent storage is updated correctly after successful execution and remains unchanged after failed transactions.
Testing boundary conditions and unexpected inputs where applicable.
Keeping the tests deterministic, isolated, and easy to review.

Where appropriate, I'll cover scenarios such as:

Invalid or unauthorized callers.
Invalid input values or missing required state.
Repeated or duplicate operations.
Boundary values for numeric fields.
Storage integrity before and after contract execution.
Regression cases for previously established behavior.

I'll also verify that any emitted events or state changes remain consistent with the contract's public API if the implementation exposes them.

Before submitting the PR, I'll run the project's full validation pipeline, including:

cargo fmt
cargo clippy (if required by the repository)
cargo test --all

to ensure there are no warnings, compilation issues, or regressions across the workspace.

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

[drips-wave]

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

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