-
Notifications
You must be signed in to change notification settings - Fork 17
Feature/setup vitest testing #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/setup vitest testing #39
Conversation
|
@shruthideepikareddy is attempting to deploy a commit to the Akash Kumar's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The test setup looks good. While you've included a basic test for the homepage, do you plan to create test cases for all pages? |
|
Thanks for the feedback! I'll get right on it and i will add unit tests for the remaining pages like About, Contact, Download, Leaderboard, Privacy, and Terms , i will cover everything we have till now then I'll push the updates. |
|
I have finished the updates. |
|
Looks good, thanks for your contributions! Please join our Discord server: https://discord.gg/Qtgskdk5 |
Description:
This PR establishes a robust unit testing foundation for the BrowsePing web application using Vitest and React Testing Library. It includes the necessary configuration for Next.js 15 compatibility, path alias support, and a sample test suite. Additionally, it addresses several pre-existing linting issues and synchronizes the branch with the latest upstream changes.
Type of Change:
Related Issue
Closes #32
Testing Done
Unit Tests: Executed npm test. Result: PASS.
Linting: Executed npm run lint. Result: 0 errors.
Build: Executed npm run build. Result: Successful production build.
Verified in local Windows environment.
Screenshots (if applicable)
N/A (Testing infrastructure and lint fixes)
Checklist
I have read and followed all guidelines in CONTRIBUTING.md
My commits follow Conventional Commits format
I have tested my changes thoroughly
CRITICAL: Only my intended changes are included
I have updated relevant documentation
I have now implemented comprehensive unit tests for the About, Contact, Download, Leaderboard, Privacy, and Terms of Service pages. The localized tests, linting, and build are all passing successfully.