useTransactionQuery has no tests: query state and refetch logic is uncovered

[nanaf6203-bit]

useTransactionQuery has no tests: query state and refetch logic is uncovered

Labels / Complexity: testing · Medium Complexity — Medium

Problem

useTransactionQuery (src/hooks/useTransactionQuery.ts) wraps transaction data fetching with loading/error/refetch state. It has no tests. A regression that drops the error state or breaks refetch ships silently in every screen that lists transactions.

Why this is architecturally hard

1. Query state is the test design. Tests must pin loading → data, loading → error, and refetch transitions with a stubbed fetcher.
2. The data source is the mock (i add sample readme #9). Tests written now should assert against the current fetch contract so the mock-to-real migration cannot silently change the hook's behavior.

Acceptance criteria

• Tests cover loading, success, error, and refetch states with a stubbed fetcher.
• Tests run in CI via npm test.

Out of scope

The transactions API mock (#9); other hooks.

Getting started

• src/hooks/useTransactionQuery.ts — the hook
• src/hooks/__tests__/useToast.test.ts — the pattern

Commands: npm test.

Good first files to read: src/hooks/useTransactionQuery.ts.

[esegbueadam-sys]

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

Hi, maintainer. I would like to work on your project.

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

[1Judah]

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

I am applying for issue 877 to implement the described solution, reviewing the relevant source files first and delivering changes that satisfy the acceptance criteria while ensuring all tests pass.

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

[pchieneye]

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

I have reviewed this issue and understand the requirements.

I'd be happy to work on it. Please assign it to me.

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

[drips-wave]

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

🧑‍💻 @1Judah: 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 @1Judah as part of the Stellar Wave Program's 8th Wave 🥳

😎 @1Judah: 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.