AnalyticsService and ReputationService have zero test files between them

[chonilius]

There is no analytics.service.spec.ts, analytics.controller.spec.ts, reputation.service.spec.ts, or reputation.controller.spec.ts anywhere in the repository — a full find across src/ confirms neither the analytics nor reputation module has a single spec file, stub or otherwise. This is distinct from #21 (which is about reputation snapshots being vulnerable to gaming, a specific exploit concern) and from #56/#20 (auth module coverage, general near-zero-coverage framing) — this is the narrower, concrete fact that two entire modules containing non-trivial aggregation logic (heatmap bucketing, top-client ranking, completion-rate/on-time-delivery percentage math, org/language extraction) have literally no automated test of any kind.

Given both services independently reimplement similar bounty-filtering-and-aggregation logic (forContributor and computeAndSave compute overlapping stats — merge rate/completion rate, avg review time — from slightly different code paths), the lack of tests means these two implementations can silently drift apart with no test to catch the divergence.

Fix: add baseline spec files for both services covering at minimum the merge-rate/completion-rate math, the heatmap date-bucketing, and the empty-input (zero bounties) edge cases where both currently short-circuit to 0.

[Chigybillionz]

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

Hi, I’m interested in this task and can handle the implementation. Assign it to me and I’ll get started.

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

[gbotemipeter14]

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

Hi, I reviewed #140, the missing test coverage for AnalyticsService and ReputationService. I understand there are currently no spec files for either the analytics or reputation modules, despite both containing non-trivial aggregation logic (heatmap date-bucketing, merge-rate/completion-rate math, and org/language extraction), and that both services independently reimplement similar bounty-filtering-and-aggregation logic that could silently drift apart without tests to catch it. I understand the fix requires adding baseline spec files covering at minimum the merge-rate/completion-rate math, the heatmap date-bucketing, and the empty-input edge cases where both currently short-circuit to 0. I'd like to work on this and can get started right away.

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

[zane1502]

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

Hello, I would like to work on this

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

[drips-wave]

Congratulations, @zane1502! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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