Add integration test for trade history endpoint returning results filtered by date range

[Chucks1093]

Summary

The trade history endpoint accepts optional from and to date parameters but has no integration test confirming the filter works correctly. A test should seed trades across multiple dates and assert the response only includes trades within the specified range.

Scope

• Seed five trades: two before the range, one inside, two after
• Call the endpoint with from and to params enclosing only the middle trade
• Assert exactly one trade is returned and it matches the expected trade
• Assert trades outside the range are absent from the response

Acceptance Criteria

• Only trades within the date range returned
• Trades before from absent from response
• Trades after to absent from response
• Boundary trades (exactly on from and to) included

ETA: 12 hours

---

Coordinate on Telegram

[jbeloved700]

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

Hi maintainer I will like to work on this issue

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

[stacyelliott492-star]

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

Hey dear maintainer i would love to work on this issue please grant
help the needy

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

[bandanadivya]

@bandanadivya 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 if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

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

[Chuks-coderr]

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

i would like to work on this issue

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

[Menjay7]

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

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

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

[Tundeakinbami-dev]

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

I would like to work on this issue

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

[drips-wave]

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

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