E2E Integration Test Coverage Tracker (Meta-Issue)

[Josue19-08]

🔖 Title

E2E Integration Test Coverage Tracker (Meta-Issue)

---

📄 Description

This is a meta-issue to track end-to-end integration test coverage for all critical user flows in the API. Each flow has its own independent sub-issue that can be completed by different contributors when the corresponding features are implemented. This issue will be closed only when all sub-issues are completed and all critical user journeys are tested.

This issue does NOT need to be implemented directly - instead, contributors should work on the individual sub-issues listed below.

---

✅ Sub-Issues to Track

Authentication Flow

• E2E Tests for Authentication Flow #76 - E2E Tests for Authentication Flow

Loan Management Flow

• E2E Tests for Loan Lifecycle Flow #77 - E2E Tests for Loan Lifecycle Flow

Liquidity Provider Flow

• E2E Tests for Liquidity Operations Flow #78 - E2E Tests for Liquidity Operations Flow

Notifications Flow

• E2E Tests for Notifications Flow #79 - E2E Tests for Notifications Flow

Transaction Handling Flow

• E2E Tests for Transaction Submission Flow #80 - E2E Tests for Transaction Submission Flow

---

📚 Documentation/context for AI

(This link never should removed)
https://github.com/TrustUp-app/TrustUp-API/tree/main/docs

Relevant documentation:

• https://github.com/TrustUp-app/TrustUp-API/blob/main/docs/development/testing-structure.md
• https://github.com/TrustUp-app/TrustUp-API/blob/main/docs/architecture/overview.md

---

🗒️ Additional notes

Completion Criteria:

• All sub-issues (E2E Tests for Authentication Flow #76-E2E Tests for Transaction Submission Flow #80) are closed
• All critical user flows have E2E test coverage
• Tests validate HTTP responses and database state changes
• CI/CD pipeline runs E2E tests successfully

For Contributors:
Do not work on this meta-issue directly. Instead, pick one of the sub-issues above that corresponds to a flow you've implemented or want to test.

[BrayanMQ]

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

Hi! I’d be happy to work on this issue. I have experience contributing to collaborative projects and have also acted as a maintainer, which has given me strong skills in understanding requirements, managing issues, and delivering reliable, well-scoped solutions.

I’m a Computer Science Engineer and full-stack developer with solid experience implementing solutions across both backend and frontend, including designing and integrating APIs. I mainly work with React, TypeScript, Node.js, and C#, and I enjoy building scalable features and collaborating closely with other contributors to deliver high-quality results.

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

[drips-wave]

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

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