Unit Tests for NotificationsService

[Josue19-08]

🔖 Title

Unit Tests for NotificationsService

---

📄 Description

Write comprehensive unit tests for the NotificationsService covering notification listing, filtering, and marking as read. Mock database operations. This issue can be completed independently once issues #60 and #61 are implemented.

Related to: Meta-issue #67

---

✅ Tasks to complete

• Test listing notifications for a user
• Test filtering notifications by read/unread status
• Test filtering notifications by type
• Test pagination of notification list
• Test unread count calculation
• Test marking individual notification as read
• Test marking all notifications as read
• Test validation of notification ownership
• Test handling of non-existent notification IDs
• Test handling of empty notification lists
• Mock database queries
• Achieve 80%+ coverage for NotificationsService

---

📚 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/database-schema.md

Dependencies:

• Issue User Notifications List Endpoint #60 (List notifications) should be implemented
• Issue Mark Notifications as Read Endpoints #61 (Mark as read) should be implemented

---

🗒️ Additional notes

Acceptance Criteria:

• All test cases pass
• Code coverage for NotificationsService is at least 80%
• Database operations are properly mocked
• Filtering and pagination logic is validated
• Ownership validation is tested
• Edge cases (empty lists, invalid IDs) are covered

[OsejiFabian]

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

i would like to work on this issue please

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

[drips-wave]

Congratulations, @OsejiFabian! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[OsejiFabian]

I HAVE WORK ON THE ISSUE BUT WHEN I PUSH THE PR IT SHOWS A NEW BRANCH I HAVE TRIED TO MERGE THEM BUT IT IS STILL THESAME , I HAVE TRIED MULTIPLE FIXES BUT IT STILL REMAIN THE SAME, YOU CAN LOOK AT THE DEVELOPMENT SECTION UNDER ASSIGNEE TO SEE THE TWO LINK/BRANCH