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
Whenever a bean override (such as for @TestBean, @MockitoBean, and @MockitoSpyBean) cannot be selected "by type", we should improve diagnostics for users by pointing out (in the exception's message) that the type selection might have failed because the runtime type of the target bean could not be inferred.
sbrannen
changed the title
Improve exception message when a Bean Override cannot be selected by type
Improve diagnostics when a Bean Override cannot be selected by type
Dec 2, 2024
quaff
added a commit
to quaff/spring-framework
that referenced
this issue
Dec 3, 2024
Overview
Whenever a bean override (such as for
@TestBean
,@MockitoBean
, and@MockitoSpyBean
) cannot be selected "by type", we should improve diagnostics for users by pointing out (in the exception's message) that the type selection might have failed because the runtime type of the target bean could not be inferred.Related Issues
@MockitoSpyBean
requires existing bean instance to spy on #33935@MockitoSpyBean
#33965The text was updated successfully, but these errors were encountered: