Add Tests for Zero-Deadline and No-Deadline Bounties

[Jagadeeshftw]

Description:

Expand bounty escrow tests to explicitly cover bounties created with zero deadline and with no deadline specified, validating how refund and eligibility logic behaves in each case.

Requirements and context:

• Deadline is optional, but behavior may differ for zero vs None
• Need tests that:
  • Create bounties with deadline = 0, Some(ts), and None
  • Verify refund rules for each case
• Component location:
  • contracts/bounty_escrow/contracts/escrow/src/lib.rs
  • Bounty tests

Suggested execution:

1. Fork the repo and create a branch

   git checkout -b test/zero-and-no-deadline-bounties

2. Implement changes

   • Add focused tests for the three deadline configurations
   • Confirm consistent and documented behavior

3. Test and commit

   • Run bounty tests
   • Document deadline semantics in PR

Example commit message:

test: add tests for zero-deadline and no-deadline bounties

Guidelines:

• Assignment required before starting
• PR description must include: Closes #[issue_id]

[Josetic224]

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

Hi,

I’d like to take this on. Handling the distinction between 0 and None is a common friction point in Soroban/Rust, especially regarding how the env.ledger().timestamp() interacts with refund logic.

My plan for the test suite:

Scenario Matrix: I’ll implement focused tests for the three states: deadline = 0, Some(timestamp), and None.

Refund Logic Validation: I’ll specifically verify the "early refund" vs. "expired" logic. For example, ensuring that deadline = 0 doesn't inadvertently allow an immediate refund before a bounty can be completed, and checking if None correctly acts as a "perpetual" bounty.

Eligibility Checks: I'll assert that submission functions don't prematurely lock out users when the deadline is omitted.

Documentation: As suggested, I’ll document the observed semantics in the PR to ensure the "intended" behavior is clear for future contributors.

I can have these tests ready for review by tomorrow. Can you assign this to me

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

[drips-wave]

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

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

[Josetic224]

Thanks I have started immediately

[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

[sanmipaul]

@sanmipaul has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would like to work on this issue.

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

[Awointa]

@Awointa has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi 👋

I’d like to take this on. I’ll add tests covering zero deadline, explicit deadline, and no deadline cases, and verify refund and eligibility behavior for each.

I’ll ensure the behavior is consistent, well-tested, and clearly documented in the PR.

Please assign this issue so I can get started. Thanks!

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

[Trovic1]

@Trovic1 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi! I’d like to take on this task. I can expand the bounty escrow tests in lib.rs to cover zero, Some(ts), and None deadline configurations. I'll focus on validating consistent refund behavior across all three cases and ensure the semantics are clearly documented in the PR.

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

[BrayanMQ]

@BrayanMQ has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi! I’d be happy to work on this issue. I have experience contributing to collaborative projects and have also acted as a maintainer, which has given me strong skills in understanding requirements, managing issues, and delivering reliable, well-scoped solutions.

I’m a Computer Science Engineer and full-stack developer with solid experience implementing solutions across both backend and frontend, including designing and integrating APIs. I mainly work with React, TypeScript, Node.js, and C#, and I enjoy building scalable features and collaborating closely with other contributors to deliver high-quality results.

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