Support running logical tests as part of the build phase of a scheme

Originator:markos
Number:rdar://15871179 Date Originated:21-Jan-2014 06:38 PM
Status:Closed Resolved:
Product:Developer Tools Product Version:5.0.2
Classification:Enhancement Reproducible:Always
 
Summary:
Since Xcode 5 and the deprecation of the flag "TEST_AFTER_BUILD" for test targets, it is not possible to have logical tests running as part of a build.

This was possible in Xcode 4.

Steps to Reproduce:
1 Install Xcode 5.0.2
2 Create an "Empty Application" project
3 Select the "*Tests" target
3.1 Select "Build Settings"
3.2 Remove "Test Host"
3.3 Remove "Bundle loader"
3.4 Select "Build Phases"
3.5 Under "Target Dependencies" remove main target
3.6 Under "Compile Sources" add the single .m file "*AppDelegate.m"
4 Select "Product", "Scheme", "Manage Schemes"
5 Select the single scheme available
6 Select the "Build" phase
7 Check the "Run" box under the "*Tests" target
8 Select the simulator as a destination
9 CMD+B to build



Expected Results:
To have logical tests run as part of build

Actual Results:
Logical tests are not running as part of the build

Version:
Xcode 5.0.2
Build version 5A3005

OS X 10.9.1 (13B42)


Notes:
No known workarounds to have logical tests run as part of a build

Configuration:


Attachments:
'LogicalTestsAsPartOfBuildPhaseInScheme-Xcode4.6.3.zip' and 'LogicalTestsAsPartOfBuildPhaseInScheme.zip' were successfully uploaded.

Comments

Apple Developer Relations 03-Nov-2014 08:57 PM

Engineering has determined that there are no plans to address this issue.

We are now closing this bug report.

If you have questions regarding the resolution of this issue, please update your bug report with that information.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!