[Test] horizonAccount.ts has no test file

[collinsezedike]

Description

No horizonAccount.test.ts exists in apps/web/src/__tests__/lib/ (only wallet.test.ts and lobstr-wallet.test.ts are present). fetchBalances (apps/web/src/lib/horizonAccount.ts:9) returns null when the Horizon response isn't ok, and horizonUrlFor's mainnet/testnet branch (lines 1-5) is also untested.

Acceptance Criteria

• A new test mocks fetch to return a non-ok response and asserts fetchBalances resolves to null rather than throwing.
• A test asserts horizonUrlFor("mainnet") returns the Horizon mainnet URL and any other value returns the testnet URL.
• pnpm test (apps/web package) passes.

[belloaliyu11]

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

Hello Maintainer, I’d love to take ownership of this issue and submit a high-quality pull request once completed.

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

[Timmmytunner]

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

Hello Maintainer, I’ve reviewed the issue and understand what is required. I’d be happy to take it on and work toward a solid solution.

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

[ibochivincent-lang]

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

I’d like to work on Issue #658 because horizonAccount.ts contains important wallet-balance and network-selection logic that currently has no direct test coverage. In particular, the failure behavior of fetchBalances and the mainnet/testnet URL selection could regress without being detected.

I will first review apps/web/src/lib/horizonAccount.ts and the existing tests under apps/web/src/__tests__/lib/ to follow the project's established mocking and assertion patterns.

I will then add horizonAccount.test.ts covering the two behaviors identified in the issue.

For fetchBalances, I will mock fetch to return a non-OK HTTP response and verify that the function resolves to null rather than throwing. I will also ensure the mock is isolated so the test does not affect other tests that rely on the global fetch implementation.

For horizonUrlFor, I will verify that "mainnet" resolves to the configured Horizon mainnet URL and that other supported/non-mainnet values follow the existing testnet branch. This will pin the conditional behavior without coupling the test to unrelated implementation details.

I will keep the tests focused on observable behavior and avoid introducing unnecessary integration dependencies or network requests.

Finally, I will run the new test file together with the apps/web test suite using pnpm test and verify that the complete package test suite remains green.

My goal is to give horizonAccount.ts direct regression coverage for both its network URL selection and graceful handling of Horizon failures, ensuring wallet balance fetching remains predictable without relying on live Horizon requests.

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

[DevTobis]

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

assign me this issue, i will quickly resolve

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

[drips-wave]

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

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