test: Toast render and auto-dismiss, Tooltip hover/focus visibility, Dashboard controlled and defaultSection navigation

[k-deejah]

Problem

1. Tests for Toast component render, auto-dismiss, and manual close are missing — after issue e08 adds Toast, no tests verify the toast renders with the correct message, auto-dismisses after the configured duration, or the close button dismisses it immediately.

2. Tests for Tooltip component render and keyboard accessibility are missing — after issue e10 adds Tooltip, no tests verify the tooltip content appears on hover/focus, is hidden by default, or is accessible via keyboard focus on the trigger element.

3. Tests for Dashboard controlled navigation (activeSection/onSectionChange) and defaultSection prop are missing — after issue e12, no tests verify that passing activeSection="transactions" renders TransactionsScreen, onSectionChange fires when a nav item is clicked, or defaultSection="soroban" initialises to the Soroban screen.

Solution

Write Vitest + @testing-library/react tests for all three groups using userEvent.hover, userEvent.tab, and mock props.

Acceptance Criteria

• Toast render, auto-dismiss, and manual close tests pass
• Tooltip visibility on hover/focus and hidden-by-default tests pass
• Dashboard controlled and uncontrolled navigation tests pass
• All tests pass with npm test

---

Note for Contributors: Write a clear PR description. Include the full npm test output and describe how you tested the Tooltip keyboard focus behaviour using userEvent.tab().

[Ivenkili]

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

Hey maintainer,
i would love to solve this, kindly assign

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

[Viky207]

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

hello please can i work on this issue

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

[divysam]

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

Hello
I would love to work on this issue please

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

[chukwunazannakenyi-netizen]

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

hi maintainer i will like to work on this please
i promise to submit pr earlier

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

[jadonamite]

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

hi maintainer please can i fix this

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

[drips-wave]

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

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

[jadonamite]

Working through this one, all three groups turn out to be either already covered or blocked upstream. Flagging rather than opening a PR that duplicates existing work:

1. Toast render / auto-dismiss / manual close — already covered. Toast has landed on main along with src/components/ui/Toast.test.tsx, which tests render, auto-dismiss after the configured duration, and manual close. Worth noting its "auto-dismisses after duration" case is currently failing on a clean checkout of 5bc3678 — that looks like a real bug or a fake-timer issue in the existing test rather than missing coverage. Happy to take that on if you'd like it as its own issue.

2. Tooltip hover/focus visibility — blocked. There is no Tooltip component in the codebase. NetworkSwitcher, SorobanInvokeButton, and AccountCard each hand-roll their own show/hide state instead. Building the shared component is #406 (currently unassigned), so writing it here would land someone else's issue inside a test PR. Once #406 exists I'll add the hover/focus/userEvent.tab() coverage.

3. Dashboard controlled + defaultSection navigation — covered in #420, which adds the props and ships src/screens/Dashboard.test.tsx with exactly these cases: activeSection="transactions" renders TransactionsScreen, onSectionChange fires on nav click (and does not move the view in controlled mode), and defaultSection="soroban" initialises to the Soroban screen.

So the only genuinely outstanding work is group 2, gated on #406. Let me know if you'd prefer I pick up #406 and then come back to this, or leave this open until someone claims it.

One related note while I was in here: Sidebar restores a persisted section from localStorage on mount and calls onNavigate with it. In controlled mode that surfaces as one unprompted onSectionChange shortly after mount, which may not be intended now that #420 adds controlled navigation.