Closed mrehan27 closed 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 52.54%. Comparing base (
48c64c9
) to head (72de5cb
). Report is 39 commits behind head on feature/cdp.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Build available to test
Version: rehan-test-improvements-part-3-SNAPSHOT
Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/
No changes detected in SDK binary size ✅
part of: MBL-215
Background
I noticed we have been using both
Mockito
andMockK
in Data Pipelines module. While this isn't necessarily an issue, we should only use both if needed. For functionalities that can be handled by both, we should stick to our preferred choice for consistency. I preferMockK
overMockito
because:MockK
is more Kotlin-friendly and easier to integrateI haven't removed
Mockito
from the module yet, I only updated it to see how it works. If everything goes well, we can later removeMockito
from the module/project.Changes
MockK
for mocking objects instead ofMockito
Mockito
withMockK