Nabble - jMock

Re: how to test property of argument passed to method?

2008-10-04T20:27:43Z

On Thu, Oct 2, 2008 at 5:38 PM, Dale King <dalewking@...> wrote:

Which could then be used as

one(mock).myMethod( with(Bob.class, hasProperty("prop", equalTo("value") ) );

This is very close to what I was originally trying to do, and quite readable.

Re: how to test property of argument passed to method?

2008-10-02T14:38:08Z

It sure seems like something could be done in the API to make it simpler, but I'm not sure what. So let me think out loud here.

What we really want is the ability to explicitly specify the type parameter like in C++ where you could say

with< Bob >( hasProperty(...) )

Java does have explicit type parameters for methods, but it only works if qualified with this for an instance method or the class name for static methods (See <http://www.angelikalanger.com/GenericsFAQ/FAQSections/TechnicalDetails.html#What%20explicit%20type%20argument%20specification?>). You would have to do something like this:

this.< Bob >with( hasProperty(...) )

It seems you could accomplish the same thing just using casting since with is going to return null any way:

   one(mock).myMethod( (Bob)with(hasProperty("prop", equalTo("value") ) );

I have said it before, but I think the generic parameter on Matcher was a bad idea and adds no value. At the very least there should have been non-generic matchers and generic ones are subinterface of that. hasProperty should return the non-generic Matcher while some other method could return a generic one. Then you can overload differently based on generic or non-generic.

Perhaps it might be good to have a with method that takes a class parameter (Note I used ... to allow multiple Matchers that are anded together):

   T with( Class<T> clazz, Matcher< ? >... matcher )

This is essentially the same as:

     (T)with( allOf( is( clazz ), allOf( matcher ) ) ) );

Which could then be used as

one(mock).myMethod( with(Bob.class, hasProperty("prop", equalTo("value") ) );

On Thu, Oct 2, 2008 at 3:54 PM, Limbic System <limbicsystem@...> wrote:

Nat,

Thanks for your speedy reply. Too bad the generics don't allow that syntax, but at least now I can stop banging my head against the desk. :-)

L

On Thu, Oct 2, 2008 at 1:37 AM, Nat Pryce <nat.pryce@...> wrote:
Unfortunately, Java's generics are crap, so while the following doesn't compile:

one(mock).myMethod(with(hasProperty("prop", eq("value"))));

The following does:

Matcher<Bob> propEqualToValue = hasProperty("prop", equalTo("value");
one(mock).myMethod(with(propEqualToValue));

Maybe they'll make generics work one day, but until then we'll have to
use awkward workarounds like that.

--Nat

2008/10/2 Limbic System <limbicsystem@...>:

> What is the proper way to test a property of an argument passed into a
> method of a mock, under JMock 2.5?
> Let's say that my CUT would normally be called like:
> myObject.myMethod(arg);
> and I'd like to verify that "arg" is of a particular type, and that it has a
> particular property set. I'm trying to do this:
> one(mock).myMethod(with(hasProperty("prop", eq("value"))));
> but hasProperty() returns Object, while myMethod() is expecting type
> Argument.
> I *can* do the following, which works:
> one(mock).myMethod(with(any(Argument.class)));
> I've been googling this problem for 2 days now, so any help would be greatly
> appreciated, thanks.
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

--
Dale King

Nabble - jMock

Re: how to test property of argument passed to method?

Re: how to test property of argument passed to method?

Re: how to test property of argument passed to method?

Re: how to test property of argument passed to method?

how to test property of argument passed to method?

Re: "java.lang.IllegalArgumentException: a mock with name ... already exists" with jmock2.5.0

Re: "java.lang.IllegalArgumentException: a mock with name ... already exists" with jmock2.5.0

"java.lang.IllegalArgumentException: a mock with name ... already exists" with jmock2.5.0

Re: how to test exception condition in Junit

how to test exception condition in Junit

[jira] Closed: (JMOCK-204) Documentation does not use the oneOf method

Re: writing test case for struts action?

Re: writing test case for struts action?

writing test case for struts action?

[jira] Updated: (JMOCK-203) CardinalityClause does not include new oneOf method

[jira] Resolved: (JMOCK-203) CardinalityClause does not include new oneOf method

[jira] Updated: (JMOCK-203) CardinalityClause does not include new oneOf method

[jira] Created: (JMOCK-205) Deprecate the 'one' method in favour of 'oneOf'

[jira] Updated: (JMOCK-204) Documentation does not use the oneOf method

[jira] Created: (JMOCK-204) Documentation does not use the oneOf method

[jira] Updated: (JMOCK-202) Unsatisfied expectations are not correctly captured with JUnit4's @Test(expected=AssertionError.class) in JMock 2.5.0-RC1+

[jira] Commented: (JMOCK-203) CardinalityClause does not include new oneOf method

[jira] Created: (JMOCK-203) CardinalityClause does not include new oneOf method

Re: Can I mock an enum

Re: Can I mock an enum

Re: Re: Can I mock an enum