Write tests for AddressDisplay truncation copy-to-clipboard and clipboard fallback

[k-deejah]

Problem

src/components/AddressDisplay.tsx has three distinct testable behaviors with zero coverage: the address is truncated by default using truncateAddress() from src/lib/utils.ts, the copy button calls navigator.clipboard.writeText, and the button aria-label changes to "Copied!" after a successful copy.

The known bug where the copy operation silently fails in non-HTTPS contexts also has no regression test. Without a test that mocks a rejected clipboard promise, any fix to the fallback behavior can be reverted without detection. A third untested behavior: the 2-second reset timeout that changes the aria-label back from "Copied!" to the default — if the timeout is accidentally removed, the label stays "Copied!" forever.

Solution

Write React Testing Library + @testing-library/user-event tests for AddressDisplay. Mock navigator.clipboard using vi.stubGlobal. Test:

• Truncated address is displayed by default (not the full 56-char Stellar address)
• Clicking the copy button calls navigator.clipboard.writeText with the full address
• The copy button aria-label changes to "Copied!" immediately after click
• The aria-label resets back after 2 seconds (use vi.useFakeTimers)
• When clipboard.writeText rejects, the fallback document.execCommand is attempted
• No error is thrown when clipboard is unavailable

Acceptance Criteria

• Truncated address renders by default
• Copy button calls clipboard API with the full untruncated address
• aria-label updates to "Copied!" immediately after successful copy
• aria-label resets after 2 seconds using fake timers
• Clipboard rejection triggers the execCommand fallback path
• All tests pass with npm test

---

Note for Contributors: If you're assigned to this issue, write a clear and detailed description for your pull request. Explain what was changed, why it was needed, how it was implemented, and include any relevant testing or screenshots where applicable.

[tzar-deek]

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

Hi maintainer can I get on this issue for you real quick, as I am active right now on the wave I also hopes this open doors to us working on this project some more after the wave, will love to help in the course of this journey.

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

[investorUsman]

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

Hi maintainers! I’d love to take on this issue. I’m eager to make my first contribution to this project, and I have the time and consistency to get this fixed right away. Please assign it to me, and I’ll have a PR ready for review shortly!

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

[stayzappy]

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

Good Day, Please Kindly Assign this issue to me, As i have the expertise to complete it within the given timeframe

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

[drips-wave]

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

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