Fix unit test suite crash (missing jsdom) and resolve failing tests#1535
Fix unit test suite crash (missing jsdom) and resolve failing tests#1535ArshVermaGit wants to merge 1 commit into
Conversation
|
@ArshVermaGit is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
There was a problem hiding this comment.
Thanks for your first PR on DevTrack! 🎉
A maintainer will review it within 48 hours. While you wait:
- Make sure CI is passing (type-check + lint)
- Double-check the PR description is filled out and the issue is linked
- Feel free to ask questions in Discussions if you need help
If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!
ArshVermaGit
left a comment
There was a problem hiding this comment.
Hi @Priyanshu-byte-coder ! Issue #1534 has been resolved. Please review the PR and merge it under GSSoC. Thanks!
Description
This PR resolves a critical infrastructure issue where the local unit testing suite was failing to start, and patches 4 brittle tests that were failing once the suite booted up.
Resolved Issue
Resolves #1534
Fixes:
jsdomas adevDependencyto prevent Vitest from throwing a missing environment error on startup.test/user-settings-api.test.tsto include the newly addedbio: ""field, properly aligning the mock expectations with the API response.test/components/DashboardHeader.test.tsxfromgetByText(/Dashboard/i)togetByRole("heading", { name: "Dashboard" })because the test was accidentally matching the "Dashboard overview" subtitle text.How to Verify
npm installto grabjsdom.npm run test.