test(dashboard): verify empty inputs fallback states for profile optimizer

[Mohammedsami001]

Description

Fixes #2683

Added fallback verification testing to ProfileOptimizerModal. Tested the UI's resilience when missing parameters (userData = null) and empty inputs (userData = {}) are provided. During this, a runtime exception was identified on empty object inputs and fixed using optional chaining (userData.profile?.developerScore).

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• I have run npm run test and all tests pass locally.
• I have run npm run test:coverage and branch coverage is at or above 70%.
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).

[vercel]

@Mohammedsami001 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Mohammedsami001]

@JhaSourav07 👋

I have successfully resolved this issue by adding the 5 required integration test cases for ProfileOptimizerModal empty/missing inputs fallbacks. As part of this, I fixed a runtime crash in the component itself when provided with an empty object input ({}) by utilizing optional chaining (userData.profile?.developerScore). Furthermore, I implemented tests utilizing standard testing timeouts instead of fake timers to seamlessly handle the component's internal asynchronous 3.8-second loading sequence without encountering loop warnings or hydration failures. All tests are passing cleanly locally with Vitest!

Could you please review and authorize this PR when you have a moment?

Also, could you please add the necessary labels to this PR for GSSoC 2026?

Thank you!

[github-actions]

🎉 Congratulations @Mohammedsami001! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨