Expand Jest + Supertest suite: streams API contract tests

[greatest0fallt1me]

Description

Grow automated tests beyond health.test.ts: cover full streams API surface with supertest.

Requirements and context

• Use app export from index.ts without binding port where possible.
• Table-driven cases for validation errors.

Suggested execution

• Fork the repository and create a branch (example below).
• Implement changes in StreamPay-Backend (TypeScript / Express per package.json).
• Keep the service secure, tested, and documented; prefer small, reviewable PRs.

git checkout -b test/streams-api-supertest

Implementation targets

• src/__tests__/streams.test.ts (or tests/).

Tests and validation

• Aim for high branch coverage on handlers.

• Run npm test and npm run lint in StreamPay-Backend.

• Cover edge cases; include test output and brief security notes in the PR description.

Guidelines

• Target minimum 95% test coverage on new or changed backend code (or justify gaps).
• Clear documentation (OpenAPI / README / inline docs as specified).
• Timeframe: 96 hours from assignment.

Example commit message

test(backend): supertest coverage for streams endpoints

[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

[Abolax123]

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

I can expand automated tests by adding Supertest coverage for the Streams API in src/tests/streams.test.ts. The tests will use the app export from index.ts without binding a port and include table-driven cases for validation errors and edge cases. I’ll ensure high branch coverage, run npm test and npm run lint, and document results with test output and brief security notes in the PR.

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

[drips-wave]

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

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