Test – Bid Placement and Withdrawal

[Baskarayelu]

Description
Add tests for place_bid (valid, unverified investor, over limit, wrong status) and withdraw_bid (owner, non-owner, already accepted/withdrawn).

Requirements and context

• Achieve minimum 95% test coverage for bid placement and withdrawal
• Smart contracts only (Soroban/Rust)

Suggested execution

1. Fork the repo and create a branch
   git checkout -b test/bid-placement-withdrawal
2. Implement changes
   • Add tests in src/test_bid.rs or equivalent
3. Test and commit
   • Run cargo test
   • Attach test output

Example commit message
test: bid placement and withdrawal

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[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

[ayomideadeniran]

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

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)
Portfolio: https://knightsdev-portfolio.vercel.app/

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

[drips-wave]

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

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

[ayomideadeniran]

@Baskarayelu Please close this issue as completed.

[ayomideadeniran]

@Baskarayelu Please close this issue as completed.

[ayomideadeniran]

@Baskarayelu Please close this issue as completed.

[ayomideadeniran]

@Baskarayelu Please close this issue as completed.

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @ayomideadeniran as part of the Stellar Wave Program's 2nd Wave 🥳

Moderator's reason: Work was completed and merged in PR: #320

😎 @ayomideadeniran: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.