feat: unit testing demo

[sagarkoshti1990]

I have ensured that following Pull Request Checklist is taken care of before sending this PR

• Code is formatted as per format decided
• Updated acceptance criteria in tracker
• Updated test cases in test-cases-tracker

Summary by CodeRabbit

• New Features

  • Enhanced testing capabilities with Jest and coverage reporting.
  • Introduced a comprehensive test suite for the Chip component ensuring correct behavior and styling.

• Bug Fixes

  • Improved reliability of the Chip component through rigorous testing.

• Chores

  • Updated dependencies for better testing framework support.
  • Refined ESLint configuration to enhance code quality.

[coderabbitai]

Walkthrough

The changes involve significant enhancements to the testing infrastructure of the front-end application. Key updates include the transition to Jest for testing with coverage reporting, the introduction of new testing libraries, and the addition of a dedicated test file for the Chip component. These modifications aim to improve code quality and maintainability while ensuring comprehensive testing of component functionality and styling.

Changes

File Path	Change Summary
apps/front-end/package.json	Updated test script to use Jest with coverage, added Jest configuration for coverage reporting, included new dependencies for testing, and reorganized existing ones.
apps/front-end/src/component/Chip.test.js	Introduced a new test suite for the Chip component, validating rendering, props handling, and styling under various conditions.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 042d2a0 and 83c593b.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

Files selected for processing (3)

• apps/front-end/package.json (3 hunks)
• apps/front-end/src/component/Chip.test.js (1 hunks)
• package.json (1 hunks)

Additional comments not posted (5)

package.json (1)

14-14: Addition of the test script is appropriate.

The new "test": "lerna run test --stream" script enhances the testing workflow by allowing parallel execution across multiple packages, which is consistent with the existing scripts.

apps/front-end/src/component/Chip.test.js (1)

1-83: Comprehensive test coverage for the Chip component.

The tests cover various scenarios effectively, ensuring the component's functionality and styling are thoroughly validated.

apps/front-end/package.json (3)

77-77: Transition to Jest with coverage is beneficial.

Switching to "jest --coverage" enhances testing capabilities by providing detailed coverage metrics.

---

84-94: Addition of Jest configuration is well-structured.

The Jest configuration for coverage collection is comprehensive and excludes non-essential files, which helps maintain code quality.

---

136-137: Inclusion of testing libraries strengthens the testing framework.

Adding @testing-library/jest-dom, @testing-library/react, and jest improves the testing framework's capabilities.

Also applies to: 144-144