I have a problem that the Xcode IDE 6 doesn't detect my swift unit test cases correctly. When I run the unit tests, all tests were executed.
But in the IDE while editing the unit tests aren't recognized. I have to run the whole unit test suite in order to run a single test.
I couldn't figure out how I avoid this glitch.
The "fix" for me was to add a new test. I made up some nonsense:
func testThatNothing() {
XCTAssertTrue(true, "True should be true")
}
When I ran the tests again, all the tests in that file were recognized by the editor. I deleted the bogus test and it's all still fine. Unfortunately I had to do this in each file, but at least it works. Hope this helps someone.
Below are few solution for this issue :
Wait for sometime. It takes time to load diamond sometimes. Navigate between different files and then move to same test-case it should appear.
Clean project, Clean build folder and even delete derived data content. Check this how to delete derived data safely.
Quit Xcode and open it again.
Make sure that your test-case name begins with testFunc_Name
Sometimes your test-case file may contain function other than test-case. In such scenario diamond symbol doesn't appears. Remove such function.
In my case 1, 3 and 5 solution often worked for me.
(Since your comment indicates you're still having this problem after a week, this might not help you, but…)
I ran into this problem where adding a new (Swift) test in 6.1 wouldn't make it show up in the "Test Navigator" or the scheme editor -- restarting Xcode fixed the problem and now I can run the tests individually.
My full answer is here.
In Xcode 7 getting Unit Testing set up is a little easier than in Xcode 6 (no need to annotate class and methods as public). Use @testable before the import of the class name.
import XCTest
@testable import MyProject
class MyClassTests: XCTestCase {
func testMyMethod() {
let myClass = MyClass()
let sum = myClass.addTwoNumbers(1, 2)
XCTAssertEqual(sum, 3)
}
}
In your class you don't have to do anything special.
class MyClass {
func addTwoNumbers(a: Int, b: Int) -> Int {
return a + b
}
}
It is possible you may also have to set "Defines Module" under Packaging to YES for your app's Build Settings.
See also these answers:
I had a similar error (though in Objective C, not swift). If I added a new test method to the class, the new method wouldn't show up in the test navigator nor would it be executed when I ran the whole bundle. I also wouldn't get those dots in the side bar next to each method that, if clicked, would run just one test method.
The only thing fixed my problem was deleting my whole test class (saving its contents elsewhere temporarily) then recreating the test class and (perhaps more carefully?) setting the build settings all over again.
In my case I had a reference to an old test target which was causing the issue, so I got rid of the missing target and clean the solution and then my test cases were working fine.
Also make sure that the test methods you create should always start with the keyword "test" else Xcode won't be able to identify the test methods an example of the same is
func test_getPhotos_With_Good_Request_Returns_PhotoCollection(){
//ARRANGE
//ACT
//ASSERT
}
Hope it helps
