Started on some unit tests today in Xcode and decided to test my test. Turns out they always pass but not sure why.

The following should fail:

struct MyUnitTest {
    @Test func example() throws {
        XCTAssertTrue("a" == "b")
        XCTAssertEqual("a", "b")
    }
}

But they don't. Anyone know why?

Started on some unit tests today in Xcode and decided to test my test. Turns out they always pass but not sure why.

The following should fail:

struct MyUnitTest {
    @Test func example() throws {
        XCTAssertTrue("a" == "b")
        XCTAssertEqual("a", "b")
    }
}

But they don't. Anyone know why?

• swift
• unit-testing
• xctest

• You're mixing Swift testing (@Test) and XCTest, which I'm not sure is possible like this – Alexander Commented 18 hours ago
• That was it, thank you. I choose the wrong template. – Rob Bonner Commented 18 hours ago
• Swift Testing is generally preferable these days, you would just write: #expect("a" == "b") instead of the two XCTest assertions you tried. – Alexander Commented 18 hours ago

1 Answer 1

You're using Swift Testing (as indicated by the @Test and lack of XCTestCase subclass), which doesn't use XCTest assertions. Instead you'd write:

struct MyUnitTest {
    @Test func example() throws {
        #expect("a" == "b")
    }
}

If you don't need any instance variables on the struct, you can even just have the test functions at the top level without the boilerplate of a struct. The need to wrap all the test cases in a class was a limitation of Objective-C and XCTest, which no longer applies.