Add Tests for Recurring Bill next_due_date Edge Cases

[Baskarayelu]

Description:

Recurring bills set next_due_date = due_date + (frequency_days * 86400). Add tests for edge cases: frequency_days 1, 30, 365, and ensure paid_at does not affect next bill’s due_date incorrectly.

Test Cases

• frequency_days = 1: next due date is +1 day
• frequency_days = 30: next due date is +30 days
• Multiple pay cycles: due dates advance correctly for 2nd, 3rd bill

Acceptance Criteria

• Recurring date math verified by tests

[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

[bitstarkbridge]

@bitstarkbridge 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 because it directly impacts reliability and developer experience. Problems around deployment, repository configuration, and contract/network mismatches can block contributors entirely, so resolving them has immediate value for both the maintainers and the broader user base. I’m particularly motivated by issues that require careful debugging and clear documentation, since solving them not only fixes the immediate bug but also improves the overall workflow and prevents future regressions.

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

[drips-wave]

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

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

[drips-wave]

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

Moderator's reason: [Auto-assessed] The contributor provided comprehensive tests addressing all requirements of the issue, including edge cases for different frequencies, multiple pay cycles, and ensuring payment timing doesn't affect subsequent due dates. The PR was merged, and the work directly aligns with the acceptance criteria.

😎 @bitstarkbridge: 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.