gmane.comp.java.jmock.user

2.6.0-RC1 uploaded

Steve Freeman — 2008-12-04T00:05:16

please spread the word and take it for a spin. S. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: jmock 1.2 disregarding skipped stubs

mikeottinger — 2008-12-03T01:21:50

Hi Steve, thanks for the reply, the exception doesn't occur in setup, it occurs in the method I'm actually testing. Specifically, I wasn't mocking a transactionManager properly and when the method attempted to begin a transaction it failed, thus causing all of my method's dependencies to not be called. But... as to your question regarding expectations... yes! I added them and I get my failures when I should. Thanks so much. Steve Freeman-2 wrote:

Re: jmock 1.2 disregarding skipped stubs

Steve Freeman — 2008-12-03T00:20:43

To clarify, if the test setup is throwing an exception, where is it being caught? Also, remember that stubs() aren't verified. They don't fail if you don't call them. Should you have some expectations? S On 3 Dec 2008, at 00:06, mikeottinger wrote: Steve Freeman Winner of the Agile Alliance Gordon Pask award 2006 http://www.m3p.co.uk M3P Limited. Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ. Company registered in England & Wales. Number 03689627 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

jmock 1.2 disregarding skipped stubs

mikeottinger — 2008-12-03T00:06:51

Hello, we're using jmock 1.2 for our mocking. I came to the realization that certain tests were passing when they should have been failing. We extend org.jmock.cglib.MockObjectTestCase to proxy classes. Our tests then use the standard: myMock.stubs().method("methodName").will(returnValue(new Foo())) When I debugged when of my tests, I realized it was throwing an exception therefore bypassing all of the method calls my test had stubbed. I would have thought that this would result in an error as none of the expectations were met. Even calling .verify() off the mocks doesn't get my test to fail like it should. Because I'm extending org.jmock.cglib.MockObjectTestCase, is there something else I'm missing? Thanks in advance.

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Piers Powlesland — 2008-11-27T11:34:35

When you create a mock, as in context.mock(AnyClass.class) You may also give the mock a name, as in context.mock(AnyClass.class, "any name"); If you create two or more mocks of the same class you must give each mock a different name, as in context.mock(AnyClass.class, "Mock 1"); context.mock(AnyClass.class, "Mock 2"); The names are used in exceptions and error output. Piers Vivek R wrote: --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Steve Freeman — 2008-11-27T11:24:53

If you have two classes then you have a different problem. A code example and stack trace please, S. On 27 Nov 2008, at 10:58, Vivek R wrote: Steve Freeman Winner of the Agile Alliance Gordon Pask award 2006 http://www.m3p.co.uk M3P Limited. Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ. Company registered in England & Wales. Number 03689627 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Vivek R — 2008-11-27T10:58:32

Evn I am facing the same problem. I have 2 classes "A.request" ( class name ) and "B.request". I am not able to mock objects of these 2 classes under the same context. It throws IllegalArgumentException. What is the workaround ? viv On Thu, Nov 27, 2008 at 3:24 PM, Piers Powlesland < piers-CTiLoCoC/w8UrEfpJOqS4QSoKaMgXudwAL8bYrjMMd8< at >public.gmane.org> wrote:

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Piers Powlesland — 2008-11-27T09:54:37

Thankyou Steve and Isiah, I think I just took a large step in the world of TDD. Isaiah Perumalla (Contractor) wrote: --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

RE: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Isaiah Perumalla (Contractor — 2008-11-26T19:30:41

I also found that when you don't describe interactions in terms of your domain your interaction test become quite brittle. This why its best to never mock types you don't own (ie library classes). I worte a post with a small example showing when interactions are not described in terms of your domain then the test become brittle. http://isaiahperumalla.wordpress.com/2008/05/28/test-driven-design-using -mocks-lessons-learnt-part-2/ Hope it helps Isaiah -----Original Message----- From: Steve Freeman [mailto:steve-/6t1Ty3A97Vaa/9Udqfwiw< at >public.gmane.org] Sent: Wednesday, November 26, 2008 12:04 PM To: user-sXN/XchZ9OexIXFVlbCvtR2eb7JE58TQ< at >public.gmane.org Subject: Re: [jmock-user] java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock On 26 Nov 2008, at 17:57, Piers wrote: In which case I'd use a real Set rather than a Mock. We see a lot of people using, for example, List when what they actually mean is Street. We try to use types that we own that

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Steve Freeman — 2008-11-26T19:03:35

In which case I'd use a real Set rather than a Mock. We see a lot of people using, for example, List when what they actually mean is Street. We try to use types that we own that represent concepts in the domain, rather than built-in or library types which we keep for implementing domain types. If these domain types are defined in terms of roles, then they're often appropriate for mocking. S. Steve Freeman Winner of the Agile Alliance Gordon Pask award 2006 http://www.m3p.co.uk M3P Limited. Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ. Company registered in England & Wales. Number 03689627 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Piers — 2008-11-26T17:57:47

Thank you for your speedy reply I am mocking a set but I am also mocking some classes in the same test, so I guess I need the ClassImposteriser.My idea was to fill a real set with mock objects which will have expectations set on them. I don't understand what you mean by "describe the interaction in terms of your domain" But I would like to, could you elaborate this point? Thanks again for your help. Piers Steve Freeman wrote: --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Steve Freeman — 2008-11-26T17:38:20

JMock enforces a different name on each instance of a mock of the same type to make the failure messages obvious. The default name is the class, so when you try to create a second one, the context complains. The solution is to give each mock of the same type a name, context.mock(AType.class, "the green one"); Incidentally, are you actually mocking Set, or is that just an example? If so, 1) it's an interface so you don't need the ClassImposteriser. 2) we recommend writing interfaces that describe the interaction in terms of your domain. 3) otherwise, just use a real one and check its contents afterwards. S. On 26 Nov 2008, at 17:18, Piers wrote: Steve Freeman Winner of the Agile Alliance Gordon Pask award 2006 http://www.m3p.co.uk M3P Limited. Registered office. 2 Church Street, Burnham, Bucks, SL1 7HZ. Company registered in England & Wales. Number 03689627 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http:/

java.lang.IllegalArgumentException: a mock with name set already exists - Please help, I am new to jmock

Piers — 2008-11-26T17:18:26

Hi I am new to jmock and writing my first test resulted in the above error, I have discovered that the problem occurs when I try to create two mocks of the same class, the code below causes the Exception to be thrown at the marked line. I'm sure you must be able to create more than one mock of any class but just I can't figure out what's going on. Thank you for your help. Piers ============================================================================ import java.util.Set; import org.jmock.Mockery; import org.jmock.integration.junit4.*; import org.jmock.lib.legacy.ClassImposteriser; import org.junit.Test; import org.junit.runner.RunWith; < at >RunWith(JMock.class) public class JMockTest { private Mockery context = new JUnit4Mockery() {{ setImposteriser(ClassImposteriser.INSTANCE); }}; < at >Test public void testJMock() { Set v1 = context.mock(Set.class); Set v2 = context.mock(Set.class); //Error on this line Set v3 = context.mock(Set.class); Set v4 = context.mock(Set.class)

Re: expectactions not met / unexpected invocation?

Nino Saturnino Martinez Vazquez Wael — 2008-11-26T07:27:37

Good idea, but both GLatLngBounds and GLatLng defines equals.. Could be that they are wrongly implemented.. And currently seems so, thanks for the help. Nat Pryce wrote:

Re: expectactions not met / unexpected invocation?

Nat Pryce — 2008-11-25T20:52:22

It could be that the GLatLngBounds or GLatLng classes do not define equals. --Nat 2008/11/25 Nino Saturnino Martinez Vazquez Wael public.gmane.org>:

expectactions not met / unexpected invocation?

Nino Saturnino Martinez Vazquez Wael — 2008-11-25T20:49:49

Hi Guys Im a bit puzzled over this one, my code does call what it should but I get this exception what could be wrong?: Caused by: unexpected invocation: eventRepository.getEvents(, <0>, <400>, null) expectations: expected once, never invoked: eventRepository.getEvents(, <0>, <400>, null); return iterator over c4a3eb2e> what happened before this: nothing! testcase: mockery.checking(new Expectations() { { oneOf(eventRepository).getEvents(new GLatLngBounds(new GLatLng(-90.0, -180.0, false), new GLatLng(90.0, 180.0, false)), 0, 400, null); ArrayList theList=new ArrayList(); theList.add(new Event()); will(returnIterator(theList)); } }); tester.startPage(HomePage.class);

Re: jmock 1.2 vary method arguments per invocation

Nat Pryce — 2008-11-22T17:55:16

2008/11/22 mikeottinger public.gmane.org>: That's what an expectation *is*, so it's only specified per expectation. The onConsecutiveCalls is for when an expectation can be matched by more than one call, and you want different actions on consectuive calls. JMock 2 is similar, but the API is better (I think). --Nat --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Re: jmock 1.2 vary method arguments per invocation

mikeottinger — 2008-11-22T17:02:09

Thanks Nat, I'll go with that With the onConsecutiveCalls for establishing return values per invocation, I would've thought there'd be a way to use a similar method for establishing parameter values per invocation. Just out of curiosity, does jmock 2.5 support this better? Thanks again. Nat Pryce wrote:

Re: jmock 1.2 vary method arguments per invocation

Nat Pryce — 2008-11-22T07:27:33

Define one expectation per parameter. You can do this in a loop to avoid duplication: expects(once()).method("getOrderForId").with("1").will(returnValue(order_1)); expects(once()).method("getOrderForId").with("2").will(returnValue(order_2)); expects(once()).method("getOrderForId").with("3").will(returnValue(order_3)); --Nat 2008/11/22 mikeottinger public.gmane.org>:

jmock 1.2 vary method arguments per invocation

mikeottinger — 2008-11-22T05:01:03

Hello, I've searched and had no luck in this: I have a mock I'm trying to stub that's called multiple times within a loop. Each invocation of the mock's method call would pass in a different parameter. It's actually this simple, the method I'm testing accepts a list of order ids. The method loops through each id, retrieving it's underlying order from the database, it's this method I'm trying to stub. I had this: orderManagerMock .expects(exactly(2)).method(getOrderForId).with("1234") .will( onConsecutiveCalls( returnValue(order_1), returnValue(order_2)) ); I would have thought I could have used onConsecutiveCalls within the with() method. Anybody have any ideas on this? Do I have to update to jmock 2 for this? Thanks in advance.

RE: Sample source code for JMock 2.5

Sprague, Matthew J — 2008-11-19T15:42:01

yes thanks. I figured out my fatal flaw in my test case. noobie mistake I am sure. I didn't realize that the mock object was in charge of creating the object so I set my mock object to a new Object and JMock was complaining... rightfully so. ________________________________ From: Joseph Ford [mailto:josephpford< at >gmail.com] Sent: Wednesday, November 19, 2008 10:32 AM To: user< at >jmock.codehaus.org Subject: Re: [jmock-user] Sample source code for JMock 2.5 Matthew - Will this help you? http://opensourcetips.blogspot.com/2007/11/jmock-tests.html Regards, Joseph Ford On Wed, Nov 19, 2008 at 9:20 AM, Sprague, Matthew J paychex.com> wrote: I am looking for some source code for the cookbook and getting started examples that I can load into Eclipse and play with it. Is there anything out there for this? ________________________________ The information contained in this message may be privileged, confidential, and protected from disclosure. If