Implement Responsive Testing for User Details API Route

[anshika1179]

Description

Fixes #6814

Implemented complete Responsive Multi-device Columns & Mobile Viewport Layouts testing (app/api/user-details/route.responsive-breakpoints.test.ts) for the user-details API route.

The testing suite verifies the API responses gracefully when simulating different scenarios related to mobile app requests:

• Mocks standard mobile-width media coordinates and verifies rate limits.
• Asserts that missing inputs (like missing usernames from a reflowed form) are handled with standard 400 errors.
• Verifies that malformed mobile inputs are handled without crashing.
• Checks that missing resources (user not found) are handled gracefully (404).
• Asserts successful data fetching for responsive display.

Pillar

• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

(N/A — Test files added)

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).
• 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).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

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

A member of the Team first needs to authorize it.

[retenta-bot]

This PR introduces a robust testing suite for the user-details API route, focusing on responsive behavior across various mobile scenarios. It aligns well with previous decisions to implement responsive testing for other components, ensuring a consistent approach to mobile user experience. Great job on addressing these critical aspects! Looking forward to your contributions. 😊

[github-actions]

🚨 Hey @anshika1179, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪