'Module was not compiled for testing' when using @testable

ios swift unit-testing swift2
hgwhittle picture hgwhittle · Jun 11, 2015 · Viewed 28.7k times · Source

I'm trying to use Swift 2's new @testable declaration to expose my classes to the test target. However I'm getting this compiler error:

enter image description here

Intervals is the module that contains the classes I'm trying to expose. How do I get rid of this error?

Answer

sgaw picture sgaw · Jun 11, 2015

In your main target you need to set the Enable Testability build option to Yes.

As per the comment by @earnshavian below, this should only be used on debug builds as per apple release notes: "The Enable Testability build setting should be used only in your Debug configuration, because it prohibits optimizations that depend on not exporting internal symbols from the app or framework" https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Chapters/Introduction.html#//apple_ref/doc/uid/TP40001051-CH1-SW326

Related questions

Unit testing Swift 2.0, @testable import, and scheme targeting issues

I have recently converted my app, and unit tests over to Swift 2.0. I am using @testable import AppName in my Tests.swift files. Due to an issue with not being able to execute subclasses in multiple targets (see here for …

Read More
iOS - 'MyProject-Swift.h' file not found when running Unit Tests for Swift

I am trying to setup Unit Testing for my project. It is an existing Objective-C app, that I have recently added one Swift class to. I have setup the 'MyProject-Swift.h' and Swift Bridging files (both 'MyProject' and 'MyProjectTest') and …

Read More
Added unit testing target to Xcode - failed to import bridging header won't go away

I added a new Test target to my Xcode project. My project has Swift code and Objective-C code, and has a bridging header. Upon either adding the bridging header to UnitTesting's build settings, or doing import MyTarget, I'm getting the …

Read More