• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Using XCTest performance tests (Debug vs Release builds)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using XCTest performance tests (Debug vs Release builds)


  • Subject: Re: Using XCTest performance tests (Debug vs Release builds)
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 07 Feb 2017 09:35:24 -0800


On Feb 7, 2017, at 12:44 AM, Chris Hanson <email@hidden> wrote:

You can actually set up Xcode to run any number or arrangement of test via the Test action this way, they don’t all have to come from a single target. So for example, you can have a single scheme for an application whose Test action runs the tests for the framework where most of the app’s logic lives, runs the unit tests for the app itself, and runs the UI tests for the app.

Yes, but it looks like all the test targets in a scheme have to share the same configuration, since there’s only a single Configuration pop-up in the Test action’s Info tab. So I couldn’t run both unit tests (Debug configuration) and performance tests (Release).

—Jens
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Using XCTest performance tests (Debug vs Release builds) (From: Jens Alfke <email@hidden>)
 >Re: Using XCTest performance tests (Debug vs Release builds) (From: Chris Hanson <email@hidden>)

  • Prev by Date: XCode codesigns my App but Gatekeeper says "unidentified developer" nonetheless
  • Next by Date: Detailed info on link-time optimization (LTO) behavior
  • Previous by thread: Re: Using XCTest performance tests (Debug vs Release builds)
  • Next by thread: Unassigned images in launch image set
  • Index(es):
    • Date
    • Thread