[Testing] Add unit tests for backend services/indexerService.ts (getIndexerStatus / resetIndexer)

[ogazboiz]

Join the discussion on Telegram

Why this matters

backend/src/services/indexerService.ts exports getIndexerStatus, resetIndexer, replayFromLedger. These are admin-facing and destructive (resetIndexer drops the cursor; replayFromLedger triggers a re-poll), but I don't see direct unit-test coverage for them in backend/tests/.

The functions are small and mockable (they only touch prisma.indexerState and sorobanEventWorker.triggerPoll).

Acceptance criteria

• Add backend/tests/indexer-service.test.ts
• Mock prisma.indexerState (Vitest module mock) and sorobanEventWorker
• Tests: getIndexerStatus returns lagSeconds=-1 when no state row, returns lagSeconds=>0 when a row exists; resetIndexer(0) upserts the row with lastCursor=null; replayFromLedger calls resetIndexer then triggerPoll
• Coverage row in the lcov report should increase

Files to touch

• new backend/tests/indexer-service.test.ts

Out of scope

• Removing the legacy indexer at services/soroban-indexer.service.ts ([Backend] Remove duplicate legacy indexer running alongside SorobanEventWorker #451)

[Michael997glitch]

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

i've resolved similar problems in the past and am confident i can implement a clean, efficient fix quickly, if am given the opportunity

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

[Thoni76]

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

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value

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

[TS-mfon]

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

Gm

Please can I work on this issue

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

[khanavi272-spec]

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

I would like to work on this issue

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

[AGWAM001]

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

Hi Maintainer would love to work on this

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

[TEEZY234]

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

I would like to work on Issue #697 – Add unit tests for backend/src/services/indexerService.ts.

I have experience writing backend unit tests with Vitest and mocking external dependencies to ensure reliable coverage of service-layer logic. This task is a good opportunity to strengthen confidence in the admin-facing indexer operations, particularly because resetIndexer and replayFromLedger can directly affect indexing behavior.

My plan is to add backend/tests/indexer-service.test.ts with focused unit tests covering the required scenarios: validating getIndexerStatus behavior when no state exists and when a state row is present, verifying that resetIndexer(0) correctly upserts the indexer state with a null cursor, and confirming that replayFromLedger invokes both resetIndexer and sorobanEventWorker.triggerPoll in the expected order. I will mock prisma.indexerState and sorobanEventWorker using Vitest module mocks to keep the tests isolated, fast, and deterministic.

The implementation will remain within the scope of the issue, follow existing project testing conventions, and aim to improve overall coverage while keeping the test suite easy to maintain.

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

[drips-wave]

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

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