18

XCode 6, Beta 5

I have a unit test like this:


    func testMyObjectsEqual()
    {
        //....

        XCTAssertEqual(myObject, myOtherObject, "\(myObject) and \(myOtherObject) should be equal")
    }

XCTAssertEqualObjects is no longer available in Swift since the language makes no distinction between scalars and objects.

So we have to use XCTAssertEqual which leads to the following error:

 "Type MyObject does not conform to protocol Equatable"

The only workaround I have found is to inherit (MyObject) from NSObject so that I can do the following:

 XCTAssert(myObject == myOtherObject, "\(myObject) and \(myOtherObject) should be equal")

So my question is: Is there a way (as of beta 5) to use XCTAssertEqual for custom types without having to rely on NSObject or littering all custom types with "==" overloads ?

joakim
  • 3,533
  • 2
  • 23
  • 28
  • I have asked a similar question that I'm wondering might be a duplicate. See http://stackoverflow.com/questions/34764509/what-is-the-replacement-for-xctassertequalobjects From what I can see XCTAssertEquals does not fire the == equivalence operator. Rather for custom classes it only returns true for object reference equality – Max MacLeod Jan 13 '16 at 10:54

2 Answers2

17

If you want to compare references in Swift, you can use === operator. This is what happens when you subclass from NSObject (when you are comparing objects in Objective-C using XCTAssertEqual, you are comparing references).

But is this really what you want?

class MyObject {
    var name: String

    init(name: String) {
        self.name = name
    }
}

func testMyObjectsEqual() {
    let myObject = MyObject(name: "obj1")
    let myOtherObject = MyObject(name: "obj1")
    let otherReferenceToMyFirstObject = myObject

    XCTAssert(myObject === myOtherObject) // fails
    XCTAssert(myObject === otherReferenceToMyFirstObject) // passes
}

I guess that when you are comparing custom objects, you probably should make them conform to the Equatable protocol and specify, when your custom objects are equal (in the following case the objects are equal when they have the same name):

class MyObject: Equatable {
    var name: String

    init(name: String) {
        self.name = name
    }
}

func ==(lhs: MyObject, rhs: MyObject) -> Bool {
    return lhs.name == rhs.name
}

func testMyObjectsEqual()
{
    let myObject = MyObject(name: "obj1")
    let myOtherObject = MyObject(name: "obj1")

    XCTAssertEqual(myObject, myOtherObject) // passes
}
Marián Černý
  • 15,096
  • 4
  • 70
  • 83
  • When it comes to comparing custom objects Apple clearly states that the responsibility for deciding when two instances qualify as equal falls on the developer. That's why they introduced the Equatable protocol. When comparing identities for reference types though, we need to use the === operator as you suggested. My problem is that we can't use XCTAssertEqual this way. – joakim Aug 16 '14 at 20:25
  • 6
    It seems to me there is a missing "XCTAssertSame" function, which would compare object equality. It's pretty easy to write though. – Robert Atkins Jan 26 '15 at 10:06
3

Since Xcode 12.5 there is XCTAssertIdentical

Piotr Tobolski
  • 1,326
  • 7
  • 22