Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Core
-
Labels:None
-
Number of attachments :
Description
Currently, EasyMock has a rule that if you supply at least one argument matcher, you must supply an argument matcher for all parameters. This gets quite cumbersome and reduces code readability when a particular method on a collaborator has many parameters, yet only one needs a matcher (like EasyMock.anyObject). I'd like to request that this rule be lifted, so that it's possible to only specify some argument matchers, and leave the rest with direct object references. I'm guessing this rule exists due to some kind of internal design constraint, so maybe it's not possible, but if it is feasible, it's make EasyMock more user-friendly IMO.