test(pr-insights): Enhance mock-integrations tests for async service layer and local cache stubs

[soumyasekharshee265-ux]

Description

Fixes #6781

This PR adds the new test file app/api/pr-insights/route.mock-integrations.test.ts targeting Asynchronous Service Layer Mocking & Local Cache Stubs for the app/api/pr-insights/route.ts route (Variation 9).

The tests use vi.mock() to stub every async boundary the route depends on — the PR insights service, the local GitHub token cache, the client IP resolver, and the abort-error type guard — so the suite stays hermetic, deterministic, and offline.

What is covered (5 test cases)

1. Standard async imports resolve — verifies the mocked fetchPRInsights service is invoked once with the trimmed username and returns the mocked payload with a 200 status.
2. Local cache queried before remote retrieval — asserts getUserGitHubToken (local cache layer) executes before fetchPRInsights (remote fetch) and that the cached token is forwarded to the downstream call.
3. Fallback on upstream timeout / abort — simulates the AbortController firing and confirms the route returns a 504 with the correct timeout message.
4. Complete success callback path — full happy-path sync from token lookup → async service → JSON response body.
5. Non-abort errors propagate as 500 — a database retrieval failure surfaces as 500 with the underlying error message.

Verification

• npm run test -- app/api/pr-insights/route.mock-integrations.test.ts → 5/5 passing ✅
• npm run format → clean ✅
• npm run lint → 0 errors in the new file ✅
• Single atomic commit following Conventional Commits ✅

Note: The unrelated pre-existing failures in app/api/streak/route.timezone-boundaries.test.ts and flaky timing assertions in utils/trustedProxy.test.ts also fail/flake on main and are not caused by this PR.

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs) — Testing (new test file for issue test(ApiPr-insightsRoute-mock-integrations): verify Asynchronous Service Layer Mocking & Local Cache Stubs (Variation 9) #6781)

Visual Preview

Not applicable — this PR adds unit tests only and does not touch any SVG output or UI.

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (npm run test -- app/api/pr-insights/route.mock-integrations.test.ts — all 5 tests pass).
• 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. (N/A — no new theme or URL parameter added)
• I have starred 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). (N/A — tests only)
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[retenta-bot]

This PR adds important test coverage for the asynchronous service layer and local cache stubs in the PR insights route. It follows a similar approach to previous decisions made regarding mock integrations, such as the tests added for types and wrapped API routes. This ensures that our testing strategy remains consistent and effective. Thank you for your contribution!

[soumyasekharshee265-ux]

Hi maintainers 👋

The failing TypeScript Type Check job is caused by pre-existing errors on main — not by this PR.

Running npm run typecheck locally on a clean main (before my changes) produces the same 4 errors in unrelated files:

app/generator/components/EditorPanel.type-compiler.test.tsx:8:50 — TS2344
app/generator/components/PreviewPanel.type-compiler.test.tsx:13:45 — TS2344
lib/rss.ts:1:20 — TS2307 (Cannot find module 'rss-parser')
lib/rss.ts:36:50 — TS7006 (Parameter 'item' implicitly has 'any' type)

None of these files are touched by this PR. My changes are limited to a single new test file:
app/api/pr-insights/route.mock-integrations.test.ts

Verification that my change is clean:

• ✅ npm run test -- app/api/pr-insights/route.mock-integrations.test.ts → 5/5 tests passing
• ✅ npm run lint → 0 errors in the new file
• ✅ npm run format → clean
• ✅ Single atomic commit following Conventional Commits

Could you please advise whether:

1. I should wait for main to be fixed and rebase, or
2. Someone can trigger a re-run once main is patched?

Happy to help fix the type errors on main in a separate PR if that's preferred. Thanks! 🙏

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3958.92 KB	3958.92 KB	0 B
Total CSS	327.67 KB	327.67 KB	0 B

[Aamod007]

Excellent work on the mock integrations test for PR insights. Testing the async service layer boundaries and local cache fallback behaviors adds great stability. However, the Vercel check is failing. Please resolve the issues and rerun the CI pipeline.

[soumyasekharshee265-ux]

Hi @Aamod007, thanks for the review! I checked the Checks tab and I don't see a Vercel check listed among the 9 checks that ran — all visible checks are passing. Could you share a screenshot or link to the failing Vercel check so I can investigate? It's possible the Vercel bot isn't running on PRs from forks. Thanks!

[Aamod007]

Upon re-evaluation, I realized I previously misinterpreted the Vercel deployment failure as an issue with this PR. The Vercel build failure seems unrelated to the changes introduced here, so I will ignore it moving forward. The rest of the PR looks good, so I'm approving it!

[github-actions]

🎉 Congratulations @soumyasekharshee265-ux! 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! 💻✨