jest testing setup done

[rabiulkhan7224]

Summary by CodeRabbit

• Tests

  • Configured testing infrastructure including framework setup and required tooling.

• Chores

  • Upgraded Next.js from 15.5.0 to version 16.1.3.
  • Upgraded React and React DOM from 19.1.0 to version 19.2.3.
  • Updated TypeScript compiler configuration and related type definitions.
  • Added development dependencies and configured development tools.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR establishes testing infrastructure for a Next.js project. It introduces Jest configuration with TypeScript support, coverage collection, and environment setup. Testing library dependencies are added alongside upgrades to Next.js (v16.1.3) and React (v19.2.3). TypeScript configuration is updated to use react-jsx runtime.

Changes

Cohort / File(s)	Summary
Jest Configuration & Setup jest.config.ts, jest.setup.ts	Adds Jest configuration with nextJest wrapper, V8 coverage collection, jsdom environment, module alias mappings, and exclusion patterns. Separate setup file imports testing-library/jest-dom for DOM matchers.
Package Dependencies package.json	Adds test script ("jest"), testing dependencies (@testing-library/react, @testing-library/jest-dom, @testing-library/dom, jest, jest-environment-jsdom, @types/jest), and upgrades Next.js (15.5.0 → 16.1.3), React (19.1.0 → 19.2.3), React DOM (19.1.0 → 19.2.3), and type packages.
TypeScript Configuration tsconfig.json	Reformats lib entries and path aliases across multiple lines. Changes JSX runtime from "preserve" to "react-jsx". Extends include pattern to add ".next/dev/types/**/*.ts".

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A Jest in jest, we've woven well,
With testing threads a tale to tell,
TypeScript hops through configs new,
React and Next now tested true!
Coverage runs where bugs once dwelt, 🧪

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: setting up Jest testing infrastructure with configuration files, setup file, and test dependencies.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@jest.config.ts`:
- Around line 34-37: The moduleNameMapper currently only maps
"@/components/(.*)" which misses the project-wide "@/..." alias; update
moduleNameMapper to include a catch-all mapping for the "@/..." alias (e.g., add
a mapping for "^@/(.*)$" -> "<rootDir>/$1") so imports like "@/lib/*",
"@/utils/*", "@/hooks/*" resolve correctly, leaving the existing
"@/components/(.*)" mapping intact if desired.

In `@package.json`:
- Line 29: The package version for eslint-config-next is out of sync with
Next.js; update the dependency "eslint-config-next" in package.json to match
Next.js's major version (e.g., change "eslint-config-next": "15.5.0" to a
compatible 16.x version such as "16.1.3" or "^16.1.3") so the lint rules align
with the installed "next" version, then run npm/yarn install and re-run lint to
verify no rule mismatches remain.

🧹 Nitpick comments (1)

jest.config.ts (1)

29-30: Coverage exclusion for app/** may be overly broad.

Line 29 excludes app/layout.tsx specifically, but line 30 excludes the entire app/** directory. This means no code in the app folder will be included in coverage reports. If this is intentional (e.g., only testing components/utilities), consider adding a comment to clarify. Otherwise, you may want to be more selective about which app files to exclude.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Incomplete module alias mapping.

The moduleNameMapper only maps @/components/*, but tsconfig.json defines @/* to map to the entire project root. This will cause resolution failures for imports like @/lib/*, @/utils/*, @/hooks/*, etc.

🔧 Suggested fix

  moduleNameMapper: {
-   // ...
-   "^@/components/(.*)$": "<rootDir>/components/$1",
+   "^@/(.*)$": "<rootDir>/$1",
  },

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	moduleNameMapper: {
	// ...
	"^@/components/(.*)$": "<rootDir>/components/$1",
	},
	moduleNameMapper: {
	"^@/(.*)$": "<rootDir>/$1",
	},

🤖 Prompt for AI Agents

In `@jest.config.ts` around lines 34 - 37, The moduleNameMapper currently only
maps "@/components/(.*)" which misses the project-wide "@/..." alias; update
moduleNameMapper to include a catch-all mapping for the "@/..." alias (e.g., add
a mapping for "^@/(.*)$" -> "<rootDir>/$1") so imports like "@/lib/*",
"@/utils/*", "@/hooks/*" resolve correctly, leaving the existing
"@/components/(.*)" mapping intact if desired.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Version mismatch: eslint-config-next should match the Next.js major version.

eslint-config-next is at 15.5.0 while next is ^16.1.3. This mismatch can cause lint rules to be out of sync with the framework version.

🔧 Suggested fix

-    "eslint-config-next": "15.5.0",
+    "eslint-config-next": "^16.1.3",

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"eslint-config-next": "15.5.0",
	"eslint-config-next": "^16.1.3",

🤖 Prompt for AI Agents

In `@package.json` at line 29, The package version for eslint-config-next is out
of sync with Next.js; update the dependency "eslint-config-next" in package.json
to match Next.js's major version (e.g., change "eslint-config-next": "15.5.0" to
a compatible 16.x version such as "16.1.3" or "^16.1.3") so the lint rules align
with the installed "next" version, then run npm/yarn install and re-run lint to
verify no rule mismatches remain.