Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>My first recommendation is that you should not test your libraries. From what I read in your example, you are basically checking that <code>AFHTTPRequestOperation</code> is working as documented, but that’s not your responsability to test. You should test that you invoke AFNetworking correctly, and that given an <code>responseObject</code> or an error, your code behaves as you expect. </p> <p>Anyway, about what you are seeing, you have two “shoulds” in the same line: <code>shouldEventually</code> and <code>shouldBeNil</code>; they use to have <code>beNil</code> matcher, which is unavailable in 2.1, and I think they are bringing back. You can find the discussion in <a href="https://github.com/allending/Kiwi/issues/293" rel="nofollow">https://github.com/allending/Kiwi/issues/293</a></p> <p>Maybe you can try the following to make sure that the failure branch is not taken:</p> <pre><code>[operation setCompletionBlockWithSuccess:^(AFHTTPRequestOperation *operation, id responseObject) { testResponseObject = [[NSString alloc] initWithData:responseObject encoding:NSUTF8StringEncoding]; } failure:^(AFHTTPRequestOperation *operation, NSError *error) { // This will fail if we ever reach this branch [error shouldBeNil]; }]; [apiClient enqueueHTTPRequestOperation:operation]; [[expectFutureValue(testResponseObject) shouldEventuallyBeforeTimingOutAfter(100)] equal:@"Expected Content"]; </code></pre> <p>The <code>shouldEventuallyBeforeTimingOutAfter</code> will keep the test case “alive” waiting to check the response, but if you ever go through the failure branch, the other expectation will fail (and also the one in response will fail after 100 seconds). Hope it helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POKiwi - Expected subject to be nil, got KWAsyncVerifier
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USyonosoytu
    1. USyonosoytu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@yonosoyty indeed, I used an another should for matching because I saw that beNil is not available anymore & I guessed that they merged shouldBeNil with beNil. Anyhow my idea is to write tests for the communication with the API, in case they check with one run if they made some changes ..
      singulars
      1. PO
      1. USKex
    2. COI think you could just remove the expectation on testError. Due to the structure of your test, you can assume that testError will always be nil as long as testResponseObject has the expected value. The only way both variables could be non-nil is if *both* your success and failure blocks are called; I would say it's reasonable to assume this would never happen.
      singulars
      1. PO
      1. USMike Mertsock
    3. COI’m with @esker, testing for the successful branch should be enough, but look at my update, if you really need to check for the failure branch.
      singulars
      1. PO
      1. USyonosoytu
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload