[Testing] Create comprehensive test helpers for ESM mock patterns

[devin-ai-integration]

Domain: Testing

---

Issue [Feature] Create comprehensive test helpers for ESM mock patterns

Tier: 🟡 Medium

Description:

• Problem: Multiple test files independently define the same mock objects for stellar.service.js, users.model.js, telemetry.model.js, infra/socket/io.js, etc. Each mock must include ALL named exports from the real module or ESM resolution fails. This has caused 48+ test failures across the suite because individual test files forget to include exports like getStellarExplorerUrl, UserRole, Telemetry, or bulkIngestTelemetry.
• Implementation: Create a tests/helpers/mocks.ts file that exports complete, reusable mock factories:
  • createStellarServiceMock() — returns all 4 exports
  • createUsersModelMock() — returns UserModel, OrganizationModel, UserRole, OrganizationType
  • createTelemetryModelMock() — returns Telemetry, TelemetryAnchorStatus
  • createSocketIoMock() — returns all 5 socket functions
    Each factory returns a complete mock object. Test files import and use these factories, ensuring no exports are forgotten.

Dependencies:

• Depends on None

Acceptance Criteria:

• tests/helpers/mocks.ts exports factory functions for all commonly-mocked modules.
• Each factory returns ALL named exports from the real module.
• At least 3 test files are migrated to use the helpers as examples.
• Documentation in the helpers file explains the pattern.

Testing Requirements:

• All migrated test files pass with the new helpers.
• Run npm test to confirm no regressions.

PR Checklist:

• Branch is named conventionally (e.g., feature/issue-XX-test-mock-helpers).
• npm run lint and npm run build pass with zero warnings.
• Screenshot of passing Jest terminal logs is attached to the PR.

[Bug-Hunter-X]

@Bug-Hunter-X has applied to work on this issue as part of the Stellar Wave Program's 6th wave.


I understand the expected outcome and would love to work on this. I'll provide a solution that satisfies the acceptance criteria.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bug-Hunter-X to this issue.

[Goodnessukaigwe]

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

I will like to work on this issue

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

[drips-wave]

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

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