Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Possible bug with captures() #30
Migrated from: CodeHaus issue EASYMOCK-19
I think I may have run into a possible bug with using captures() to capture a parameter passed to a mocked method.
I've attached a (very simplified) test case to prove the behavior.
Please note that this is just a simplified test case - I know that I could specify the exact value of the arguments I expect passed to my mock, but in my real code the arguments are complex objects with a number of fields, and in the unit test (of the class using the mocked component), I want to capture the object so I can assert against just a few of those fields without re-creating the entire object in my test case.
Can someone please confirm if this is indeed a bug or if I am simply using this method wrong?