-
-
Notifications
You must be signed in to change notification settings - Fork 864
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
Write Unittests for src/components/EventManagement/EventAgendaItems/EventAgendaItems.tsx (fixes : #2366) #2975
Write Unittests for src/components/EventManagement/EventAgendaItems/EventAgendaItems.tsx (fixes : #2366) #2975
Conversation
WalkthroughThis pull request focuses on refactoring the Changes
Assessment against linked issues
Possibly related issues
Possibly related PRs
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 using PR comments)
Other keywords and placeholders
Documentation and Community
|
Our Pull Request Approval ProcessThanks for contributing! Testing Your CodeRemember, your PRs won't be reviewed until these criteria are met:
Our policies make our code better. ReviewersDo not assign reviewers. Our Queue Monitors will review your PR and assign them.
Reviewing Your CodeYour reviewer(s) will have the following roles:
CONTRIBUTING.mdRead our CONTRIBUTING.md file. Most importantly:
Other
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/components/EventManagement/EventAgendaItems/EventAgendaItems.spec.tsx (1)
Line range hint
154-208
: Consider re-enabling the commented-out toast assertion to validate user feedback.The test accurately simulates user interaction but leaves the success toast assertion commented out. Re-enabling and verifying the toast message would bolster this test’s thoroughness. For instance, you can rely on Vitest’s mock calls to confirm that
toast.success
is invoked properly.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/components/EventManagement/EventAgendaItems/EventAgendaItems.spec.tsx
(2 hunks)
🔇 Additional comments (1)
src/components/EventManagement/EventAgendaItems/EventAgendaItems.spec.tsx (1)
21-21
: Good use of Vitest's mocking utilities.
Switching from Jest to Vitest while maintaining a similar top-level mocking approach looks clean. Ensure you remove any leftover Jest-specific imports or calls throughout the file to avoid conflicts.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop-postgres #2975 +/- ##
=====================================================
+ Coverage 29.27% 88.92% +59.65%
=====================================================
Files 300 321 +21
Lines 7546 8408 +862
Branches 1646 1835 +189
=====================================================
+ Hits 2209 7477 +5268
+ Misses 5154 688 -4466
- Partials 183 243 +60 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the CodeCov report, the coverage hasn't changed.
You have removed code, not added to the testing. When updating pleas post a screen shot of the code coverage report. It needs to get to 100% without ignore statements
There isn’t an issue assigned to you for this PR. Please follow the guidelines in our PR_GUIDELINES.md file. We have the procedures in place so that everyone has a fair chance of contributing. I will be closing this pull request. Please follow the procedures and resubmit when ready. |
@palisadoes You did assign this to me. If possible, I would be happy to continue working on this development. |
I'm sorry. |
Reopening. I lost track. |
@palisadoes I'm unable to identify additional test cases for this component. If you could suggest areas or scenarios to focus on, I would really appreciate it. |
@noman2002 PTAL |
@noman2002 Hi, Did you find any area for new testcases ? |
6e3435b
into
PalisadoesFoundation:develop-postgres
What kind of change does this PR introduce?
Migration of unit test written in jest to vitest.
Issue Number:
Fixes #2366
Did you add tests for your changes?
Yes
Snapshots/Videos:
If relevant, did you update the documentation?
Does this PR introduce a breaking change?
No
Other information
No
Have you read the contributing guide?
Yes
Summary by CodeRabbit
Bug Fixes
New Features