search for: jmock2

...66 + sid jessie Bug #717166 [openswan-modules-dkms] openswan-modules-dkms: Fails to build against Linux 3.10-1 Added tag(s) sid and jessie. > tags 717116 + sid jessie Bug #717116 [jbossas4] jbossas4: FTBFS with Java7 Added tag(s) sid and jessie. > tags 717122 + sid jessie Bug #717122 [jetty8] jmock2: FTBFS with Java7 Added tag(s) sid and jessie. > tags 717138 + sid jessie Bug #717138 [lightproof] lightproof: dummy bug to prevent migrating to testing before LO 4.0.4-3 Added tag(s) sid and jessie. > thanks Stopping processing here. Please contact me if you need assistance. -- 717116: htt...

I wanted to draw attention to this bug report [A] which highlights a change that was made between Mocha 0.4 and 0.5. It may have lead to tests which pass unexpectedly. Does my explanation (below) make sense to people? It feels like we should at least add some warnings to the documentation. You are correct that this behaviour did change between Mocha v0.4.0 and > v0.5.0 (in revision 115).

...know that since revision 193 (which is included in gem 0.5.6), the > initializer block syntax has been available. Unfortunately the rdoc > didn''t get updated until revision 221 (which hasn''t yet been > released). > > Since your email, I''ve added support for JMock2 style sequences [1] > and states [2] which allow you to constrain the order of invocation. I > haven''t yet sorted out the error reporting and there may be some > teething problems, but feel free to give it a try. All the rdoc has > been updated in trunk. See AutoVerify#sequence...

I was reading through the FlexMock docs and noticed the expectation method .mock, which returns the original mock associated with an expectation. It looks really handy for writing nice all-in-one mocks like: mock_user = mock(''User'').expects(:first_name).returns(''Jonah'').mock So I started playing around with mocha and found I could actually already do this!