You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just upgraded to the latest version of jmockit (1.45) and jUnit (5.4.0) and all the sudden all test were failing with a null pointer exception I checked and none of the objects injected by jmockit using annotations @tested, @injected and @mocked were being created, they were all null hence the null pointer exception I downgraded JUnit back to 5.3..2 and everything was working again.
Any suggestion with this?
The text was updated successfully, but these errors were encountered:
ramses-gomez
changed the title
Having problems with jmockit 145 and Junit 5..4
Having problems with jmockit 1.45 and Junit 5..4
Feb 15, 2019
rliesenfeld
changed the title
Having problems with jmockit 1.45 and Junit 5..4
Having problems with jmockit 1.45 and Junit 5.4
Feb 16, 2019
As I explained in junit-team/junit5#1792 (comment), the JMockitInitialization class does not properly register JMockit's FakeExtensionRegistry which in turn never gets a chance to register the JMockitExtension.
Thus, JMockit's support for JUnit Jupiter simply never gets registered when using JUnit Jupiter 5.4+.
I just upgraded to the latest version of jmockit (1.45) and jUnit (5.4.0) and all the sudden all test were failing with a null pointer exception I checked and none of the objects injected by jmockit using annotations @tested, @injected and @mocked were being created, they were all null hence the null pointer exception I downgraded JUnit back to 5.3..2 and everything was working again.
Any suggestion with this?
The text was updated successfully, but these errors were encountered: