Skip to content
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

add Unittests for lib/widgets/event_card.dart #2669

Merged

Conversation

sayyad-asifbasha
Copy link

@sayyad-asifbasha sayyad-asifbasha commented Dec 17, 2024

What kind of change does this PR introduce?

Unittests for lib/widgets/event_card.dart

Issue Number:

Fixes #2618

Did you add tests for your changes?

Yes

Snapshots/Videos:
Screenshot 2024-12-17 222343

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Tests
    • Added test cases for the EventCard widget to verify visibility of the "Created" row based on the current user's status as the event creator.
    • Ensured correct behavior of the "Created" row and verified icon when the current user is not the event creator.

Copy link
Contributor

coderabbitai bot commented Dec 17, 2024

Walkthrough

The pull request adds two new test cases for the EventCard widget in the event_card_test.dart file. These tests specifically verify the visibility of the "Created" row and verified icon based on the event creator's status. The tests use mockNetworkImages to handle network image loading during widget testing, ensuring comprehensive coverage of the widget's behavior under different user scenarios.

Changes

File Change Summary
test/widget_tests/widgets/event_card_test.dart Added two new test cases:
1. Verifies "Created" row visibility when current user is the event creator
2. Checks absence of "Created" row when current user is not the event creator

Assessment against linked issues

Objective Addressed Explanation
100% Coverage for event_card.dart [#2618] Partial progress made, but full coverage not yet confirmed
Comprehensive Widget Testing [#2618] Added specific test scenarios for event card widget
Maintain Existing Functionality [#2618] No functionality removed in the tests

Possibly related PRs

Suggested reviewers

  • noman2002
  • palisadoes
  • Dante291

Poem

🐰 A rabbit's tale of testing might,
Event cards dancing in widget light,
Created rows now clearly seen,
Visibility tested, coverage keen,
CodeRabbit hops with pure delight! 🧪


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d9e297 and 9398e71.

📒 Files selected for processing (1)
  • test/widget_tests/widgets/event_card_test.dart (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/widget_tests/widgets/event_card_test.dart

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
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

Other

🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
test/widget_tests/widgets/event_card_test.dart (2)

199-212: Add test cleanup and improve test description

The test correctly verifies the Created row visibility, but could be improved:

  1. Add tearDown to reset userConfig.currentUser.id after the test
  2. Consider a more descriptive test name like "should show Created row and verified icon when current user is the event creator"
+  tearDown(() {
+    userConfig.currentUser.id = null; // or default value
+  });

-  testWidgets('Check for Created Row visibility', (tester) async {
+  testWidgets('should show Created row and verified icon when current user is the event creator', 
    (tester) async {

198-228: Consider adding edge case tests

While the current test coverage is good, consider adding these edge cases:

  1. Test with null creator
  2. Test with empty location/description
  3. Test with very long text content to verify truncation
  4. Test with different date formats

Would you like me to provide example test cases for these scenarios?

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e73d1c1 and 6d9e297.

📒 Files selected for processing (1)
  • test/widget_tests/widgets/event_card_test.dart (1 hunks)

test/widget_tests/widgets/event_card_test.dart Outdated Show resolved Hide resolved
Copy link

codecov bot commented Dec 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.10%. Comparing base (e73d1c1) to head (9398e71).
Report is 9 commits behind head on develop-postgres.

Additional details and impacted files
@@                 Coverage Diff                  @@
##           develop-postgres    #2669      +/-   ##
====================================================
+ Coverage             95.94%   96.10%   +0.16%     
====================================================
  Files                   187      187              
  Lines                  9887     9887              
====================================================
+ Hits                   9486     9502      +16     
+ Misses                  401      385      -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@palisadoes
Copy link
Contributor

  1. Please fix the failing tests. Click on the Details links for more information.
  2. Please make sure that CodeRabbit.ai approves your changes

coderabbitai[bot]
coderabbitai bot previously approved these changes Dec 18, 2024
@palisadoes
Copy link
Contributor

@noman2002 PTAL

@sayyad-asifbasha
Copy link
Author

@noman2002 please review.

Copy link
Contributor

@Dante291 Dante291 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@palisadoes palisadoes merged commit 0e8b559 into PalisadoesFoundation:develop-postgres Dec 28, 2024
10 checks passed
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.

3 participants