Open Radar

 
Summary:
XCTAssertEquals first and second parameter cannot be an array literal, e.g.:

XCTAssertEquals(array2, @[@2,@3,@4,@5], @"Map result was not as expected");

does not work because of several compile errors.

Steps to Reproduce:
Create a XCTAssertEquals statement with an array literal as the first or second parameter.

Expected Results:
The XCTAssertEquals should compile correctly.

Actual Results:
Several compile errors:
- Expected identifier or '('
- Extraneous closing brace ('}')
- Unexpected '@' in program
- Extraneous closing brace ('}')
- Expected ']' or ','
- Unexpected token after Objective-C string

Regression:
No.

Notes:
I understand that this happens because XCTAssertEquals is a macro and results in several lines of code that will be compiled. When I enclose the array literal in parenthesis, I get the expected result. My suggestion is that you add the parenthesis in the macro realization.

This bug is also present in the other XCTAssert macros (I tested XCTAssertEqualObjects and XCTAssertEqualsNil as well).