Adding Unit Tests to an already existing project?
Solution 1
Answer updated for Xcode 10.2.
Glad you asked this question — it's never too late to add tests to a project!
- Open your targets panel by selecting your project in the navigator,
- Click the + button that's at the bottom of the target list,
- Select iOS Unit Testing Bundle under Test section in iOS tab,
- Provide the required information and click Done.
It's that simple. Xcode will generate a target, some boilerplate files such as Info.plist and an initial test case file for you. Happy testing!
Solution 2
Also, if you want to be able to do cmd-U to run your tests then delete the scheme that was created for the test bundle and instead edit your main application scheme and add the test bundle in the Test configuration. See this screenshot:
Solution 3
One more variant using Test navigator
Xcode version 10.2.1
- Open
Test navigator
(⌘ Command + 6) - + at the bottom
New Unit Test Target...
- Choose options
Do not forget add next import to test internal
[About] elements
-
#import "myClass.h"
for Objective-C -
@testable import module_name
for Swift
Solution 4
Xcode 7 update
Method one
File > New > Target...
Choose iOS Unit Testing Bundle. (If you want to add UI Testing then choose the UI Testing Bundle.)
Method two
Click your project name in the Project Navigator. You will see TARGETS listed. At the bottom of the screen press the plus (+) button and add the iOS Unit Testing Bundle.
The test targets in this image have already been added, but you can see where the add button is.
Related
Solution 5
This is pretty descriptive how-to guide: Adding Unit Tests to an existing iOS project with Xcode 4
Randall
Updated on July 08, 2022Comments
-
Randall almost 2 years
When you create an XCode 4 project, it asks you if you want to include unit testing. But how do you add it to a project that's been created without them?
I started a project with Unit Tests to try to figure it out, and it looks like the only difference between it and my existing project are the Test.h and Test.m files in the new project.
But when I move them into my old project and try to build, it says no such file or directory: SenTestingKit/SenTestingKit.h. That looks like a framework to me, but if I go to build phases and try to add the framework, there isn't one available called SenTestingKit :( And the new project only links the usual suspects: UIKit, CoreGraphics, and Foundation, but no SenTestingKit.
-
Swift Dev Journal almost 13 yearsTo clarify for the original poster, you need to add a unit testing bundle target to your project. The unit testing bundle is in the Other group under both iOS and Mac OS X.
-
akashivskyy almost 13 years@Mark: Thanks, that's what I was talking about.
-
Randall almost 13 yearsI added the target, but still when I add: new file -> Objective C Test Case Class, and try to compile, it says cannot find SenTestingKit/SenTestingKit.h.
-
Swift Dev Journal almost 13 yearsMake sure the .m file for the test case class is a member of the unit testing target. When you add a test case class to a project, Xcode's default behavior is to add the class to the application target, not the unit testing target. Select the test case class in the project navigator and open the file inspector to see the file's target membership.
-
Jay Vachhani over 12 years@kashiv, my unit test target was working fine until I added new files into project, after that it wont work on hudson (automatic build and test). my build is still success and can run the main target and unittest both in xcode, but its not working in hudson. Do I need to add those files to test target as well?
-
akashivskyy over 12 years@JayVachhani: You should check if your test .m files are members of text target.
-
Jay Vachhani over 12 years@Kashiv Yes, it is all same nothing change in unittest folder.
-
l --marc l over 4 yearsIn Xcode 11, when a test bundle target is added, then such test bundle as already listed and enable in the test section of the currently active schema. A separate test schema is not generated.