Local qualified @MethodSource
factory method name treated differently than FQMN
#3266
Closed
5 tasks done
Labels
Milestone
Overview
This issue is both a bug report and an enhancement proposal.
Bug
When the
@MethodSource
factory methods involved are overloaded, a local qualified method name (LQMN) is not treated the same as a fully-qualified method name (FQMN).Specifically, if the user provides a FQMN without specifying the parameter list, JUnit Jupiter will find the factory method that accepts zero arguments. Whereas, if the user provides an LQMN without specifying the parameter list, JUnit Jupiter will fail to find the factory method.
Enhancement
When a user provides a FQMN or LQMN without specifying the parameter list, JUnit Jupiter should fall back to the same lenient search semantics that are used to locate a "default" local factory method.
Related Issues
@MethodSource
factory method #3130@MethodSource
factory method does not support canonical array names #3131Deliverables
5.9.x
The text was updated successfully, but these errors were encountered: