[Testing] Add unit tests for backend lib/redis.ts MemoryCache.set/get/del/expire

[ogazboiz]

Join the discussion on Telegram

Why this matters

backend/src/lib/redis.ts includes a hand-rolled MemoryCache class with set/get/del/cleanup/getStats and a 60-second sweep. No tests for the cache itself.

This is the cache that fronts admin metrics, the claimable-amount fingerprinting, and the user-summary cache (indirectly). A bug here silently inflates RPC cost or stale data.

Acceptance criteria

• Add backend/tests/memory-cache.test.ts (Vitest)
• Test cases: set+get returns value, set with 0 TTL is immediately expired, expired entries are pruned by cleanup(), del() removes an entry, getStats() reflects hits/misses/itemCount, getMetadata() returns ISO timestamps
• Don't depend on real-time sleep: use fake timers (vi.useFakeTimers) to advance time
• Don't touch the Redis pub/sub paths in this issue

Files to touch

• new backend/tests/memory-cache.test.ts

Out of scope

• Testing the Redis publisher/subscriber lifecycle

[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.

[coderolisa]

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

Hello maintainer let me work on this
please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @coderolisa 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.

[Menjay7]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and I will deliver a clean, reliable solution. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Menjay7 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 #696 – Add unit tests for backend/src/lib/redis.ts MemoryCache functionality.

I have experience writing unit tests for caching systems and time-dependent logic using Vitest. Since this MemoryCache implementation is used by multiple parts of the backend, adding dedicated coverage will help prevent regressions that could lead to stale data, incorrect cache behavior, or unnecessary RPC calls.

My plan is to create backend/tests/memory-cache.test.ts and cover all acceptance criteria, including set/get, immediate expiration with zero TTL, cleanup of expired entries, entry deletion, cache statistics tracking, and metadata validation. I will use vi.useFakeTimers() and controlled time advancement to ensure the tests are deterministic and do not rely on real-time delays. The tests will remain focused on the MemoryCache implementation and will not touch the Redis pub/sub lifecycle, keeping the scope aligned with the issue requirements.

The resulting test suite will be clear, maintainable, and designed to improve confidence in the cache layer while increasing overall backend coverage.

ℹ️ 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 🌊