Add unit tests for useRelativeTime hook confirming correct output at several time distances

[Chucks1093]

Summary

The useRelativeTime hook has no unit tests. Tests should confirm the hook returns the correct relative string at several time distances and that the output updates after the 60-second refresh interval.

Scope

• Test a timestamp 30 seconds ago returns a string containing seconds
• Test a timestamp 90 seconds ago returns a string containing minute
• Test a timestamp 2 hours ago returns a string containing hours
• Test a timestamp 3 days ago returns a string containing days
• Advance fake timers by 60 seconds and assert the output string updates

Acceptance Criteria

• 30 seconds ago produces a seconds-relative string
• 90 seconds ago produces a minutes-relative string
• 2 hours ago produces an hours-relative string
• 3 days ago produces a days-relative string
• Output updates after 60-second timer interval

ETA: 12 hours

---

Coordinate on Telegram

[OpensrcLord]

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

Hello @maintainer, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me. And I will deliver at the shortest possible time.

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

[blessme247]

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

I would like to work on this issue

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

[Caneryy]

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

Hi, may I work on this issue please?

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

[yusufmuhammadayodeji-netizen]

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

Hi! I'm ready to start immediately and deliver a polished solution. Please consider assigning this issue to me

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @OpensrcLord as part of the Stellar Wave Program's 7th Wave 🥳

Moderator's reason: [Auto-assessed] The PR was successfully merged on 2026-07-26T09:30:51Z by the maintainer. The contribution adds both the requested hook and a comprehensive test suite that directly addresses every acceptance criterion, including relative time formatting at various intervals and timer-based updates.

😎 @OpensrcLord: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.