refactor(dashboard): add error boundary component test for DashboardError

[JhaSourav07]

🧩 Background

app/(root)/dashboard/error.tsx has logic to detect rate limit and not-found error types from the message string. This parsing has no tests.

🎯 Objective

Create app/(root)/dashboard/error.test.tsx verifying that the correct headline and emoji render for each error type.

📁 Files to touch

• app/(root)/dashboard/error.test.tsx (new)

🛠️ Implementation steps

• Render with error.message = 'API limit reached' → assert ⏳ emoji appears.
• Render with error.message = 'User not found' → assert 🕵️‍♂️ emoji appears.
• Render with a generic error → assert ⚠️ emoji.

✅ Definition of done

• 3 test cases.
• vitest run passes.

[HimanshuGaur14]

Hey @JhaSourav07 ,

I've looked at error.tsx before requesting — the string-based error type detection is the exact logic I'll be testing.

What I found:

• error.tsx parses error.message to distinguish rate limit, not-found, and generic errors — but this branching logic has zero test coverage currently
• Each branch renders a different headline + emoji, making it straightforward to assert via React Testing Library's getByText

What I'll add in error.test.tsx:

• Rate limit : errorerror.message = 'API limit reached'
• Not found : errorerror.message = 'User not found'
• Generic fallback : any other message

Approach:

• Render <ErrorComponent error={...} reset={() => {}} /> using @testing-library/react
• Use getByText to assert the correct emoji appears in each branch
• No mocking needed — pure render tests, fully isolated

Only 1 new file. All 3 cases cover every branch in the existing parsing logic. vitest run will pass.

Please assign this issue to me if you liked my approach and proposed solution.Thank u.

[JhaSourav07]

/assign @HimanshuGaur14

[github-actions]

✅ Successfully assigned issue to @HimanshuGaur14

💡 Please read CONTRIBUTING.md if you haven't already. Good luck! 🚀

[github-actions]

Hey @JhaSourav07! 🤖

My semantic scan detected that this issue might be a duplicate of #336 (Similarity: 88.2%).

Please check between these issues and close this one if it is a duplicate.

[AvikRay1001]

/claim

[github-actions]

❌ This issue is already assigned to @HimanshuGaur14

[aryan24cse109-dev]

Hi @JhaSourav07 I see this issue is assigned to @HimanshuGaur14, but I'm highly interested in contributing to it for GSSoC 2026!

I completely understand the objective: creating the new app/(root)/dashboard/error.test.tsx file to test the error boundary parsing logic using @testing-library/react. I'll make sure to thoroughly cover all three cases (API limit reached ⏳, User not found 🕵️‍♂️, and generic fallback ⚠️) and ensure vitest run passes smoothly.

If multiple PRs are welcome or if the issue becomes available, please let me know so I can submit my solution. Thank you!"