Skip to content

chore: add unit tests for core components and update build config #339

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

AmirAliAzimloo
Copy link

📝 Description

This PR enhances the testing setup and improves build configuration to streamline the development process. It includes adding unit tests for key components, setting up mocking utilities, and updating configuration files for better maintainability and developer productivity.

🔧 Changes Made

  • 🧪 Added unit tests for the Button, Tooltip, and Home components.
  • 🧩 Implemented a mock for ResizeObserver to support JSDOM testing.
  • 🗂️ Updated tsconfig.json with path mapping for cleaner import aliases.
  • 🔧 Added test watch and coverage scripts in package.json for improved developer workflow.
  • 🐛 Fixed the Tailwind CSS import path in layout.tsx to prevent build issues.

🛠 Technical Details

  • 🔧 tsconfig.json: Added paths configuration to support module aliasing.
  • 🧪 Created test files for core components and integrated ResizeObserver mocking.
  • 📦 Updated package.json scripts to include test:watch and test:coverage.
  • 🐛 Corrected Tailwind CSS import paths to align with Next.js configuration.

🖼️ Test Coverage

Test Coverage

🗒 Additional Notes

These improvements enhance test coverage, code maintainability, and developer experience by streamlining workflows and ensuring proper configuration for testing and build processes.

Copy link

vercel bot commented May 30, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-enterprise ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 30, 2025 9:59am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants