Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I tried a couple different approaches this morning:</p> <ol> <li><p>Using a <code>UIDevice</code> category that is only linked to my test target. In that category I would override <code>currentDevice</code> with a <code>partialMock</code> implementation (<code>OCMock</code>) and stub the necessary method so that it returns Pad or Phone forcedly to my specifics tests. It should have work, but its very difficult to mess with classes such as <code>UIDevice</code> or <code>UIApplication</code>, the simulator often crashes which is a bad sign.</p></li> <li><p><code>#undef UI_INTERFACE_IDIOM()</code> and <code>#define</code> it on my test <code>.pch</code>. Pointing <code>UI_INTERFACE_IDIOM()</code> implementation in the test to a singleton instance of my own, that I could set to Pad or Phone accordingly. That worked, but the main problem is that when you run the tests the simulator also goes up ( application tests that is ) so if you are running your tests on the iPad, your test will pass, but other parts of the simulator will fail because of the contraditory responses it gets from <code>UI_INTERFACE_IDIOM()</code> (one of such is the loading of nib's specific to iPhone if you are in a universal app environment )</p></li> <li><p>I think this is the best approach. As everything in computer science, just put another layer in =) Instead of your code using <code>UI_INTERFACE_IDIOM()</code> to assess if it is on a Pad or Phone device, encapsulate this logic in a object that you can mock during your tests. That way <code>UI_INTERFACE_IDIOM()</code> will still be available to the rest of the simulator. Your production code will actually rely on it, but your tests will rely on a stubbed implementation that can respond as expected in your tests.</p></li> </ol> <p>If you want to, I can share some codes regarding this matter. And yes, this is a weary one!</p> <p>How you managed to workaround this?</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to test code that depends on UIUserInterfaceIdiom (ios)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USlindon fox
    1. USVictor Lima
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to test code that depends on UIUserInterfaceIdiom (ios)
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COWelcome to SO and nice first answer! +1. I am afraid I had given up on this one for the time being - automated testing is a dirty word in my workplace and I am more concerned with getting Source Control in place first. Having said that, I would like to get it going eventually and it seems that automated testing is much harder than it should be at the moment. Any additional details you could give would be appreciated. Thanks.
      singulars
      1. PO
      1. USlindon fox
    2. COWhatever you do, dont give up!!! Maybe this will help: http://www.amazon.com/Test-Driven-iOS-Development-Developers-Library/dp/0321774183
      singulars
      1. PO
      1. USVictor Lima
    3. COThanks for the link! I shall take a look.
      singulars
      1. PO
      1. USlindon fox
 

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