Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MockitoExtension cannot be used with JUnit 5 in OSGi integration tests
See original GitHub issueThe Mockito junit-jupiter JAR is missing OSGi bundle manifest entries so it cannot be used in OSGi integration tests.
We run some OSGi integration tests (using bnd) that have @Mocks so it would be easier if these mocks can be initialized by annotating classes with @MockitoExtension instead of using MockitoAnnotations.openMocks(this), see for example this FirmwareUpdateServiceTest.
What may complicate adding the manifest entries is that MockitoExtension is importing internal classes which aren’t exported by the mockito-core bundle. What may help is to make junit-jupiter a bundle fragment with mockito-core as host.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ve got a set of changes that makes mockito-junit-jupiter work in OSGi using the same strategy that junit5 used to identify “friend” packages that are exported but not intended for public use outside of mockito.
@raphw do you think your team would be interested?
For your edification: a) apiguardian does not bring with it any runtime dependencies (confirmed by the OSGi metadata) b) the interaction between API guardian and bnd is explained here c) the build adds a
verifyOSGigradle task glued ontocheckto make sure that future changes do not break the relationship required between mockito-core and mockito-junit-jupiter such that they continue working together in OSGi