StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20241668
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2013-11-27T11:49:00.410
FavoriteCount
0
LastActivityDate
2014-07-24T14:31:42.607
LastEditDate
2014-07-24T14:31:42.607
LastEditorUserId
77393
OwnerUserId
314848
ParentId
19398918
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
Here is how you do this in Kiwi: First, you must dependency inject <code>NetworkClass</code> to <code>TestedClass</code> (if it's not clear how, please add a comment and I'll explain; this can be done as a property for simplicity. This is so that you can operate on a mock object for the <code>NetworkClass</code>) Then your spec, create the mock for the network class and create your class that you want to unit test: <pre><code>SPEC_BEGIN(TestSpec) describe(@"describe goes here", ^{ it(@"should test block", ^{ NetworkClass *mockNetworkClass = [NetworkClass mock]; KWCaptureSpy *spy = [mockNetworkClass captureArgument:@selector(networkMethod:) atIndex:0]; TestedClass testClass = [TestedClass alloc] init]; testClass.networkClass = mockNetworkClass; [testClass testMethod]; NetworkClassCallback blockToRun = spy.argument; blockToRun(nil); // add expectations here }); }); SPEC_END </code></pre> To explain what's going on here: You are creating <code>TestedClass</code> and calling <code>testMethod</code>. However, before that, we are creating something called <code>Spy</code> - its job is to capture the block in the first parameter when <code>networkMethod:</code> is called. Now, it's time to actually execute the block itself. It's easy to be confused here so I'll emphasize this: the order of calls is important; you first declare the spy, then call the tested method, and only then you're actually calling and executing the block! This will give you the ability to check what you want as you're the one executing the block. Hope it helps for other, as it took me quite sometime to understand this flow.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to stub method block in Kiwi?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCodezy
UserOwnerUserId
1. USkernix
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to stub method block in Kiwi?
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.