Skip to content
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

Improve diagnostics when a Bean Override cannot be selected by type #34004

Open
sbrannen opened this issue Dec 2, 2024 · 0 comments · May be fixed by #34006
Open

Improve diagnostics when a Bean Override cannot be selected by type #34004

sbrannen opened this issue Dec 2, 2024 · 0 comments · May be fixed by #34006
Labels
in: test Issues in the test module type: enhancement A general enhancement
Milestone

Comments

@sbrannen
Copy link
Member

sbrannen commented Dec 2, 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

@sbrannen sbrannen added in: test Issues in the test module type: enhancement A general enhancement labels Dec 2, 2024
@sbrannen sbrannen added this to the 6.2.x milestone Dec 2, 2024
@sbrannen 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: test Issues in the test module type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant