Posts

Post marked as solved
1 Replies
Hi @imneo, in recent versions of Xcode the setting you're referring to — Environment Variables — may be specified via a test plan file, and test plan files are referenced by a scheme's Test action. To customize this setting, first go to the Test action of the scheme, click the arrow next to the test plan in the list to open it in the editor, navigate to the Configurations tab, and edit the Environment Variables setting. If this is the first time you have made edits to the test plan, you may be prompted to save the file to a location in your project.
Post not yet marked as solved
13 Replies
Test bundle targets in Xcode automatically have the relevant search path build settings configured so that they can import XCTest.framework. But libraries and frameworks which need to import XCTest require these search paths to be set manually. In Xcode 11.4 and later, you can configure this easily using just one build setting: ENABLE_TESTING_SEARCH_PATHS = YES Also known as the "Enable Testing Search Paths" setting in the Xcode project editor's Build Settings tab. This automatically configures all of the necessary search paths for non-test bundle targets in Xcode. I recommend adopting this setting for testing frameworks.
Post not yet marked as solved
1 Replies
I think the usage of backticks in that command line is causing problems in the shell (zsh). You probably want to remove those backticks and just pass the -verbose flag directly to xcodebuild.
Post marked as solved
3 Replies
Thanks for the question, yes this appears to be a bug which we will investigate further (63677197). A temporary workaround you can try is to disable all Sanitizers (e.g. ASan, TSan, UBSan) in your test plan configuration(s), which should allow the build product to be in the expected location. Other, non-sanitizer settings in the test plan may still be varied.