Xcode: preprocessor macros for conditional DEBUG / TEST code

Question

I have sections in my code (for example in the AppDelegate.m) that should not be compiled for the Unit Tests, like

#ifndef CONFIGURATION_TESTS
// Code that should not be compiled in the Unit Tests
#endif

Targets are set up by Xcode when you select 'add Unit Tests' when creating a new project. In the Project File, I have added the Flag CONFIGURATION_TESTS to the Preprocessor Macros for the MyAppTests Built-Target but not for the MyApp Target.

This was the suggested way in many posts that i've found.

But this doesn't work, because (i guess) the MyAppTests target has the MyApp target as a dependency and because AppDelegate.m is added to the MyApp target, it gets compiled with the MyApp build settings and hence, the CONFIGURATION_TESTS is not defined.

In the unit-test files the macro is defined and behaves as expected (because the test files are only build by the MyAppTests target ?)

Does anyone know how do this, i thought this would be a common problem...

"This doesn't work: 1) CONFIGURATION_TEST is always true? 2) never true? 3) works in unit test but not in app? 4) works in app but not unit tests? (inquiring minds want to know…) — geowar
– geowar, Commented Jan 1, 2013 at 18:20

MeXx · Accepted Answer · 2016-06-18 19:02:21Z

13

I've finally found the answer myself: The key is to create a new build configuration (lets call this configuration Testing)

Then you configure the values of the preprocessor macro accordingly, so for configuration Debug and Release you set CONFIGURATION_TESTS=0 and for configuration Testing, you set CONFIGURATION_TESTS=1

Finally you edit the Unit-Test schema to use Testing as build configuration. That's it :P

I've written a detailed step-by-step explanation over at my blog

edited Jun 18, 2016 at 19:02

answered Sep 3, 2013 at 12:23

MeXx

3,36526 silver badges39 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Chris Gillum Over a year ago

Dumb question: Why do you need CONFIGURATION_TESTS=0 for non-test build configurations? I left this part out and everything seemed to work fine.

Jacek Lampart · Accepted Answer · 2013-01-10 20:41:27Z

3

You need to set "CONFIGURATION_TESTS=1", not just "CONFIGURATION_TESTS"

answered Jan 10, 2013 at 20:41

Jacek Lampart

1,76113 silver badges27 bronze badges

Collectives™ on Stack Overflow

Xcode: preprocessor macros for conditional DEBUG / TEST code

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related