StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19735367
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-01T21:03:37.630
FavoriteCount
0
LastActivityDate
2013-11-01T21:03:37.630
LastEditDate
LastEditorUserId
0
OwnerUserId
2920151
ParentId
19462130
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
If you can fully specify the sequence of calls that will happen on your mock, then you won't need a <code>beforeAnyOther</code> verification mode. For example, assuming your desired behavior is... <ul> <li><code>begin</code> gets called once, then</li> <li><code>end</code> gets called once, then</li> <li><code>flush</code> gets called once</li> <li>no other calls are made on <code>tool</code></li> </ul> then the following should the job: <pre><code>// Verify that the three invocations arrived in the desired order. InOrder inOrder = inOrder(tool); inOrder.verify(tool).begin(); inOrder.verify(tool).end(); inOrder.verify(tool).flush(); // Verify that the three invocations are all we received. Mockito.verify(tool).begin(); Mockito.verify(tool).end(); Mockito.verify(tool).flush(); Mockito.verifyNoMoreInteractions(); </code></pre> On the other hand, if you have any additional calls that happen outside of the sequence you wish to verify then you're correct, Mockito can't verify that at present. So for example, if you knew you had to call <code>tool.setPenColor()</code> at some point between <code>begin</code> and <code>flush</code> but it didn't matter if this call came before or after the call to <code>end</code>, you'd be out of luck. You can handle this situation in some other mocking libraries. EasyMock makes this easiest - for example, for a sequence where <code>begin</code> comes first, <code>flush</code> comes last, and we don't care about the calls in the middle: <pre><code>DrawTool mock = EasyMock.createMock(DrawTool.class); EasyMock.checkOrder(mock, true); mock.begin(); EasyMock.expectLastCall(); EasyMock.checkOrder(mock, false); mock.end(); EasyMock.expectLastCall(); EasyMock.expect(mock.someOtherCallThatReturnsAValue()).andReturn(null); EasyMock.checkOrder(mock, true); mock.flush(); EasyMock.expectLastCall(); EasyMock.replay(mock); new Drawer().draw(tool); EasyMock.verify(mock); </code></pre> An equivalent test appears to be possible, if unwieldy, in JMock 2. It's a <a href="http://jmock.org/javadoc/jmock-1.2.0/org/jmock/builder/IdentityBuilder.html#id%28java.lang.String%29" rel="nofollow">bit</a> <a href="http://jmock.org/javadoc/jmock-1.2.0/org/jmock/builder/MatchBuilder.html#after%28java.lang.String%29" rel="nofollow">easier</a> in JMock 1, but that library is antiquated (circa JDK 1.3), so don't use it. This isn't possible in Moxie (disclaimer/shameless plug: I'm the author), but there's now a <a href="https://code.google.com/p/moxiemocks/issues/detail?id=21" rel="nofollow">todo list item</a> for that. I can't speak for the Mockito devs as to why the Mockito verification API docs are the way they are - best ask them on the mailing list. I'm sure they'd welcome a patch.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCreating a custom VerificationMode classes for Mockito
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USpobrelkey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCreating a custom VerificationMode classes for Mockito
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.