Add docs for testing conventions covering unit test structure, mocking patterns, and integration test setup

[Chucks1093]

Summary

Contributors writing new tests have no documented conventions for how tests should be structured, how to mock the wallet or API, or how to set up the integration test environment. A testing conventions document would reduce friction and keep the test suite consistent.

Scope

• Document the unit test file naming and co-location convention
• Describe the standard pattern for mocking React Query responses in unit tests
• Explain how to mock wallet connection state in component tests
• Document how to set up the integration test environment including any required providers or fixtures
• List the test utilities available (e.g. custom render functions, query client factories)

Acceptance Criteria

• Unit test naming and co-location convention documented
• React Query mock pattern documented with a code example
• Wallet mock pattern documented with a code example
• Integration test setup steps documented
• Available test utilities listed with descriptions
• Document lives in docs/ and cross-links the error handling conventions doc

ETA: 12 hours

---

Coordinate on Telegram

[Ova-Klik]

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

I deliver fast, I approach every issue with curiosity, attention to detail, and a commitment to delivering clean, maintainable, and well-tested solutions. Driven by impact, not just commits, I value clear communication, effective collaboration with maintainers, continuous learning, and delivering meaningful value to every project I contribute to.

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

[Paulo-byt]

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

Good morning, Chief Maintainer. I'd like to work on this if it's still available.

I've read the issue and have a reasonable understanding of the work involved. I'd start by reproducing the behavior locally and confirming it still occurs on main, then work back to the underlying cause before making any changes.

The PR would include tests for the described case, a check that existing behavior is unaffected, and documentation updates where relevant.

I'll follow the repo's contribution guidelines and keep this thread updated. If I run into anything ambiguous, I'll ask here rather than guess and go in the wrong direction.

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

[omarima-10]

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

Hi, my name is Omarima-10, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Create a comprehensive testing conventions document under docs/ that defines unit test naming, file co-location standards, and recommended test structure to ensure consistency across the codebase.

2. Document the standard patterns for mocking React Query responses and wallet connection state, including concise code examples that demonstrate the project's preferred testing approach for components and hooks.

3. Explain the integration test setup process, covering required providers, fixtures, environment configuration, and the available testing utilities such as custom render helpers and Query Client factories.

4. Cross-link the new guide with the existing error handling conventions documentation, verify the examples are accurate and maintainable, and ensure the documentation satisfies all stated acceptance criteria.

ETA: 10 hours

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

[IamHarrie-Labs]

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

Hey Fren!

I'd love to take on this issue. I've reviewed the requirements and have a clear implementation plan. I can document the project's testing conventions, include clear examples for the common mocking patterns and test setup, organize everything in a way that's easy for contributors to follow, and ensure all the acceptance criteria are met.

I estimate I can have a PR ready within about 4–5 hours of being assigned.

Kindly assign this to me. Thanks!

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

[frank0277]

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

Hi please please I would like to work on this

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

[Tekprecious]

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

I have experience and have reviewed the code; I can submit a PR within 2 days.

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

[Fatumayattani]

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

Hello! I’d like to work on this issue and document the project’s existing testing conventions, mocks, utilities, and integration setup.

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

[Fabulouz34]

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

Hi maintainer please I will appreciate it if I'm given this issue to work on. Please assign me I'm ready to get started
Thank you

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

[drips-wave]

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

🧑‍💻 @omarima-10: 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 completed by @omarima-10 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @omarima-10: 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. You can also Leave a review to share your experience working on this issue.

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