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

Migrate common module to Junit5 #1135

Merged
merged 6 commits into from
Nov 29, 2024

Conversation

meetmehta1198
Copy link
Contributor

@meetmehta1198 meetmehta1198 commented Aug 1, 2024

Description of what I changed

This PR migrates the common module to Junit5 and addresses a part of the issue: #1103

E2E test

TESTED:

Please replace this with a description of how you tested your PR beyond the
automated e2e/unit tests.

Checklist: I completed these to help reviewers :)

  • I have read and will follow the review process.

  • I am familiar with Google Style Guides for the language I have coded in.

    No? Please take some time and review Java and Python style guides.

  • My IDE is configured to follow the Google code styles.

    No? Unsure? -> configure your IDE.

  • I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)

  • I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.

  • All new and existing tests passed.

  • My pull request is based on the latest changes of the master branch.

    No? Unsure? -> execute command git pull --rebase upstream master

@meetmehta1198
Copy link
Contributor Author

This PR solve some of the test cases based on the Issue #1103

@chandrashekar-s

@meetmehta1198
Copy link
Contributor Author

cc @bashir2

@chandrashekar-s chandrashekar-s self-requested a review August 14, 2024 14:06
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.67%. Comparing base (b03c2c7) to head (b209ce2).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1135      +/-   ##
============================================
- Coverage     51.76%   51.67%   -0.09%     
+ Complexity      669      668       -1     
============================================
  Files            95       95              
  Lines          5612     5612              
  Branches        731      731              
============================================
- Hits           2905     2900       -5     
- Misses         2425     2430       +5     
  Partials        282      282              

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

Copy link
Collaborator

@chandrashekar-s chandrashekar-s left a comment

Choose a reason for hiding this comment

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

Thanks @meetmehta1198 for the changes and apologies for the delay in the review. There are few comments, can you please have a look.

@meetmehta1198 meetmehta1198 force-pushed the common-module-junit5 branch 2 times, most recently from 4145b99 to 7b0ecdd Compare September 9, 2024 22:45
@meetmehta1198
Copy link
Contributor Author

@chandrashekar-s can you please review this PR

Copy link
Collaborator

@chandrashekar-s chandrashekar-s left a comment

Choose a reason for hiding this comment

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

Thanks @meetmehta1198 for these changes. I am extremely sorry for delaying the review for this PR as I was involved in some activities of another project. The changes look good, there is only one minor comment. Can you please have a look at that?

@meetmehta1198 meetmehta1198 force-pushed the common-module-junit5 branch 2 times, most recently from a709fc7 to bc37de5 Compare October 26, 2024 01:03
@chandrashekar-s
Copy link
Collaborator

Hi @meetmehta1198 for the changes, there is an build error which you can see from the logs. Can you please have a look at it.

@chandrashekar-s
Copy link
Collaborator

Hi @meetmehta1198, just a reminder to look into the build issue. Please let me know if you face any issues while accessing the build logs.

@meetmehta1198
Copy link
Contributor Author

I will take a look into it! Thanks

@meetmehta1198
Copy link
Contributor Author

@chandrashekar-s I have updated the code and the build is successful. Can you please approve this PR?

@meetmehta1198 meetmehta1198 changed the title Migrate FhirStoreUtilTest to Junit5 Migrate common module to Junit5 Nov 26, 2024
Copy link
Collaborator

@chandrashekar-s chandrashekar-s left a comment

Choose a reason for hiding this comment

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

Thanks @meetmehta1198 for the changes, they all look good now. You can go ahead and merge.

@meetmehta1198
Copy link
Contributor Author

Thanks @chandrashekar-s for all the feedback and approval. Great experience working with you!

@meetmehta1198
Copy link
Contributor Author

Only those with write access to this repository can merge pull requests.

I do not have necessary permissions to merge code!

@bashir2
Copy link
Collaborator

bashir2 commented Nov 29, 2024

Thanks @meetmehta1198 for this and congratulations on your first contribution to this repo. Just one minor comment: It seems to me that from #1103 you are fixing tests under the common module only, correct? Then I guess we should change the PR description as it currently says it fixes that bug (and will close that bug upon merge).

@chandrashekar-s
Copy link
Collaborator

Thanks @meetmehta1198 for this and congratulations on your first contribution to this repo. Just one minor comment: It seems to me that from #1103 you are fixing tests under the common module only, correct? Then I guess we should change the PR description as it currently says it fixes that bug (and will close that bug upon merge).

I have updated the PR description, so that it does not close the main issue.

@chandrashekar-s chandrashekar-s merged commit cb0d1fe into google:master Nov 29, 2024
6 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.

4 participants