XCTAssertEqual is only specialized one level deep on arrays. That means that until we have conditional conformances this will not work without an overload.

It was working fine on xcode8beta2 and before that. Was this a new change to XCTest? How did it work before?

Before it was converting to NSArray, as in SR-894. That may or may not be the behavior you want, but I think it's reasonable to have to specify that explicitly (using as NSArray).

cc @jckarter

Oh. I guess the confusing part for me is that it is telling me that
[Array<Int>] != [[Int]]
Are they really different?

It's not saying that; it's that the entire argument list isn't valid. If you open up the triangle it should give you more information about why, although you might have to look in the build log for the full story. (There's definitely a usability problem here.)

ah I see, well the error is the same when the types don't match.
```
Cannot invoke 'XCTAssertEqual' with an argument list of type '([Int], [String])'
```

I am going to flat map before giving it to XCTest for now as a work around.

Has this been fixed? If so it should be closed.

Resolved by the merge of this