Databases
StackOverflow2013
Postsdbo
POXcode / iOS: Unit Tests, Schemes, and Configurations
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POXcode / iOS: Unit Tests, Schemes, and Configurations
    primarykey
    data
    text
    <p>My iOS project has five schemes: Local Development, Integration, QA, Demo, and Production. Each scheme uses a differing configuration to control things like network poll frequency, API endpoints, analytics, and so on.</p> <p>Similarly, we have five corresponding targets: Local Development, Integration, QA, Demo, and Production. Each target has several User-Defined Build Settings, which contain API keys, numeric values for timing, etc.</p> <p>Our application's <code>Info.plist</code> file uses application variables such as <code>${SOME_ENDPOINT_URL}</code> to draw in the corresponding User-Defined Build Settings.</p> <p>To retrieve the variables, I do something like the following:</p> <pre><code>[[[NSBundle mainBundle] infoDictionary] valueForKey:@"Some Endpoint URL"] </code></pre> <p>That would correspond to the User-Defined Build Setting, like this:</p> <pre><code>"Some Endpoint URL" = ${SOME_ENDPOINT_URL} </code></pre> <p>I am now looking at how to configure the project appropriately to perform unit and logic tests.</p> <p>To build out the tests to determine if the environments are configured correctly, I'm not certain what the best practice is.</p> <ul> <li>Is it correct to build out five additional Test-specific targets for each environment?</li> <li>Or is it better to override the "Run action's arguments" setting for the test component for each scheme, and provide something like an argument to specify which scheme we are looking at?</li> <li>Are there any existing references for configuring unit and logic tests for iOS projects with multiple environments? This project's complexity seems to exceed the scope of most documentation.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKevin Dickerson
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POXcode / iOS: Unit Tests, Schemes, and Configurations
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POXcode / iOS: Unit Tests, Schemes, and Configurations
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POXcode / iOS: Unit Tests, Schemes, and Configurations
      1. This table or related slice is empty.
      1. VTUpMod
    1. COApple keeps making non-backwards-compatible changes to the whole Targets/Schemes system - I think the reason you're not finding docs is that Apple intends/expects to make more of these going forwards, and is hoping to dodge the flak they'll receive. Someone at Apple seems to hate Targets especially, so I would personally go with the "use arguments" approach - Targets may be about to get nerfed (again :( ).
      singulars
      1. POXcode / iOS: Unit Tests, Schemes, and Configurations
      1. USAdam
    2. CORather than having so many different targets, why not have only one target, and five configurations? Instead of Debug and Release you would have LocalDev, Integ, QA, Demo, Prod. You could then create five schemes that build the same target, but with a different configuration.
      singulars
      1. POXcode / iOS: Unit Tests, Schemes, and Configurations
      1. USJacob Lukas
    3. CO@JacobLukas do you know of a good tutorial for what you describe. I've always avoid schemes, but sounds like they can be really useful.
      singulars
      1. POXcode / iOS: Unit Tests, Schemes, and Configurations
      1. USDogCoffee
 

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