Add unit tests for the connect wallet button showing the correct state during connection, connected, and error states

[Chucks1093]

Summary

The connect wallet button cycles through three states: idle, connecting, and connected. Unit tests should confirm the correct label, icon, and disabled state for each and that the error state shows a retry option.

Scope

• Test idle state renders 'Connect Wallet' label and is enabled
• Test connecting state renders 'Connecting…' with a spinner and is disabled
• Test connected state renders the truncated wallet address
• Test error state renders 'Failed — Try Again' with a retry button
• Assert retry button calls the connect handler again

Acceptance Criteria

• Idle state renders 'Connect Wallet' and is enabled
• Connecting state shows spinner and is disabled
• Connected state shows truncated wallet address
• Error state shows retry button
• Retry button calls the connect handler

ETA: 12 hours

---

Coordinate on Telegram

[Ukorstack]

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

I’m interested in taking this issue and can get started right away. Kindly assign it to me.

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

[Ova-Klik]

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

hello can i work on this issue please

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

[d1a-m3n]

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

I’d like to work on this issue to contribute to the project. I’ll review the requirements, implement the necessary changes, test them properly, and ensure everything works as expected.

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

[galliogy]

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

I would like to work on this issue

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

[Just-Bamford]

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

Hi maintainer
I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

[drips-wave]

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

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

😎 @Just-Bamford: 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.