[Testing] pushNotifications.ts stub implementations cause integration tests to always pass incorrectly

[RUKAYAT-CODER]

Overview

pushNotifications.ts registration stubs return true regardless of input. Integration tests that test the push registration flow always pass, even though the real backend registration is not implemented.

Specifications

Features:

• Replace stubs with a mockable implementation that can be controlled in tests
• Add integration tests that mock the backend endpoint and test both success and failure paths

Tasks:

• Implement the real registration call
• Add Jest mocks for the backend endpoint
• Write tests for: registration success, network failure, duplicate token, invalid token

Impacted Files:

• src/services/pushNotifications.ts
• __tests__/pushNotifications.test.ts

Acceptance Criteria

• Integration tests use real implementation paths with mocked HTTP
• Token registration failure is tested and handled
• Push tests do not pass when backend returns an error

[Nacho1499]

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

Hello Maintainer,

I'm Nacho, a full-stack developer with experience building and testing React Native and TypeScript applications.

I'd like to work on this issue because reliable testing is essential for maintaining application quality. I enjoy improving test suites by replacing placeholder implementations with testable, production-like logic that accurately reflects real-world behavior.

I'll replace the current stub implementation with a mockable registration flow, implement the actual backend registration call, and write comprehensive Jest integration tests covering successful registration, network failures, duplicate tokens, and invalid tokens. I'll ensure the tests exercise the real implementation while mocking only the HTTP layer, so they correctly fail when the backend returns an error and satisfy all the acceptance criteria.

I'd appreciate the opportunity to contribute. Thank you for your consideration.

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

[northersubair]

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

can i handle this?

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

[drips-wave]

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

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