-
Notifications
You must be signed in to change notification settings - Fork 1
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
9: Code cleanup and Addressing Test Debt - Adding Unit Tests for Custom Endpoints PractitionerDetails and LocationHierarchy #19
Conversation
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.
@rehammuzzamil I tried running the tests with report generation but that seems to no longer get generated correctly and we get 0% coverage. Could you please confirm on your end and investigate/fix before we merge?
|
- Remove Jupiter unit test dependency
5504d41
to
13f32d1
Compare
@rehammuzzamil I've fixed the issue with the code coverage reporting, apparently it was being caused by the Jupiter unit tests dependency introduced in the PR here. |
Resolves #9
IMPORTANT: Where possible all PRs must be linked to a Github issue
Resolves [link to issue]
Engineer Checklist
bug fixes
mvn spotless:check
to check my code follows the project'sstyle guide
mvn clean test
to confirm all new and existing testspassed.
mvn clean package
right before creating this pull request.