Open mikevelu opened 1 year ago
Describe the bug
When comparing instances of UIImage or #imageLiteral XCTAssertNoDifference doesn't provide a diff, XCTAssertEqual does.
UIImage
#imageLiteral
XCTAssertNoDifference
XCTAssertEqual
To Reproduce testExample in ImageResourceComparisonDemoTests has some assertions which show the difference ImageResourceComparisonDemo.zip
testExample
ImageResourceComparisonDemoTests
XCTAssertEqual( #imageLiteral( resourceName: "ExampleImage" ), #imageLiteral( resourceName: "ExampleImage2" ) ) // 👆 Produces this diff: /** testExample(): XCTAssertEqual failed: ("<UIImage:0x600002d50480 named(main: ExampleImage) {1200, 1200} renderingMode=automatic(original)>") is not equal to ("<UIImage:0x600002d505a0 named(main: ExampleImage2) {1200, 1200} renderingMode=automatic(original)>") */ XCTAssertNoDifference( #imageLiteral( resourceName: "ExampleImage" ), #imageLiteral( resourceName: "ExampleImage2" ) ) // 👆 Produces this diff: /** testExample(): XCTAssertNoDifference failed: … − UIImage() + UIImage() (First: −, Second: +) */
Expected behavior I'd have expected XCTAssertNoDifference to give me an indication of what the difference between the two images is, similar to what XCTAssertEqual does.
Environment
Describe the bug
When comparing instances of
UIImage
or#imageLiteral
XCTAssertNoDifference
doesn't provide a diff,XCTAssertEqual
does.To Reproduce
testExample
inImageResourceComparisonDemoTests
has some assertions which show the difference ImageResourceComparisonDemo.zipExpected behavior I'd have expected
XCTAssertNoDifference
to give me an indication of what the difference between the two images is, similar to whatXCTAssertEqual
does.Environment