Add docs for how to write unit tests for shared utility helpers

[Chucks1093]

Summary

The client has a growing set of shared utility helpers but no documented pattern for how to test them. Contributors adding new helpers often skip tests or write them inconsistently because there is no reference to follow.

Scope

• Document the test file naming convention for utils: helperName.test.ts co-located with the helper
• Explain the test runner setup and how to run only util tests
• Include a worked example test for a simple helper showing describe block, test cases, and assertions
• Add a note that pure helpers should have 100% branch coverage

Acceptance Criteria

• Naming convention and co-location pattern are documented
• Test runner command for utils is included
• Worked example covers describe block structure and assertions
• Branch coverage expectation is stated

ETA: 12 hours

---

Coordinate on Telegram

[JClark011]

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

Hello Maintainer, I’ve reviewed the issue description and I’m confident I can work on it effectively. Please assign it to me.

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

[wheval]

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

Hello i would love to work on this.

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

[wagmiiii]

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

please i need this issue

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

[extolkom]

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

Please assign me

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

[Johnpii1]

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

Hello Sir,

I came across your project and I’m really interested in contributing.

I have experience with React for building responsive, user-friendly interfaces, and I’m also familiar with smart contracts and blockchain basics. I focus on writing clean, scalable code and improving user experience.

I’m a fast learner and ready to get started immediately. Please let me know the next steps.

Thank you.

Best regards,
Johnpaul

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

[drips-wave]

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

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