[Testing] Consolidate duplicate/overlapping indexer integration test files

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

There are overlapping integration suites covering the same indexer → stream flows:

• backend/src/__tests__/integration/streams.test.ts (242 lines)
• backend/tests/integration/streams.test.ts (425 lines)
• backend/tests/integration/stream-lifecycle.test.ts (701 lines)

The first two share near-identical describe('Indexer → stream_created …') blocks. The src/__tests__/ location is also inconsistent with the rest of the suite (everything else lives under tests/), yet vitest.config.ts includes both tests/** and src/__tests__/**. This duplicates run time and maintenance.

Acceptance criteria

• Identify the canonical suite and remove/merge the duplicate(s)
• Move any unique cases from src/__tests__/integration/streams.test.ts into tests/integration/ before deleting
• Optionally narrow vitest.config.ts include to a single test root
• npx vitest run is green with no lost coverage

Files to touch

• backend/src/__tests__/integration/streams.test.ts
• backend/tests/integration/streams.test.ts
• backend/tests/integration/stream-lifecycle.test.ts
• backend/vitest.config.ts

Out of scope

• Coverage threshold work ([Testing] Raise backend coverage back to 60% and restore thresholds #533).

[Senorespecial]

please assign this project to me i have experience in it and can deliver professionally

[Deyanju23]

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

I would like to resolve this issue please.

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

[martoniel]

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

Good day Big Dev! Pls I would love to work on this issue carefully and make PR within 24hrs

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

[wheval]

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

Hello i would love to work on this.

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

[bigvictoh]

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

I would love to work on this issue and contribute to the project.

I’ve reviewed the details and feel confident that I can investigate and implement a solid solution for this.

If this issue is currently unassigned and open for external contributors, could you please assign it to me? I will get started on a fix right away and submit a Pull Request as soon as it's ready.

Please let me know if there are any specific guidelines or approaches you'd like me to follow for this particular task.

Thanks,

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

[drips-wave]

Congratulations, @wheval! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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