Add unit tests for global error boundary confirming fallback renders and retry resets the boundary

[Chucks1093]

Summary

The global root error boundary has no unit tests. Tests should confirm the fallback UI renders when a child component throws, the retry button resets the boundary, and the boundary resets automatically on route change.

Scope

• Render a component that throws inside the root error boundary
• Assert the fallback UI is visible and the throwing component is not
• Click the retry button and assert the boundary resets and the component attempts to remount
• Simulate a route change and assert the boundary resets without user interaction

Acceptance Criteria

• Fallback UI renders when child throws
• Throwing component not visible during fallback
• Retry button resets the boundary
• Route change resets the boundary automatically

ETA: 12 hours

---

Coordinate on Telegram

[jotel-dev]

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

Kindly assign me

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

[edehvalentine236-jpg]

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

Kindly assign.

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

[cythecode]

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

Hello! I've carefully reviewed every aspect of this issue and understand what's expected. I'm committed to providing a scalable, maintainable solution with proper testing and attention to detail. Kindly assign this issue to me.

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

[drips-wave]

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

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