Tests/ParseSwiftTests/ParseUserTests.swift (1)

1010-1054: ⚡ Quick win

Optional: Consider adding error path test for completeness.

The test validates that success callbacks execute on the provided callbackQueue. While issue #431 reported that error callbacks were already correctly dispatched, adding a test for the error path would prevent future regressions and provide complete coverage of queue dispatch behavior.

Example pattern:

// Mock an error response and verify error callback runs on callbackQueue
MockURLProtocol.mockRequests { _ in
    let parseError = ParseError(code: .objectNotFound, message: "Not found")
    let encoded = try! ParseCoding.jsonEncoder().encode(parseError)
    return MockURLResponse(data: encoded, statusCode: 404, delay: 0.0)
}
user.save(options: [], callbackQueue: callbackQueue) { result in
    XCTAssertEqual(DispatchQueue.getSpecific(key: callbackKey), callbackValue)
    // validate error...
}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Tests/ParseSwiftTests/ParseUserTests.swift` around lines 1010 - 1054, Add a
companion test to testSaveAsyncCallbackQueueOnSuccess that verifies the error
callback is dispatched to the provided callbackQueue: mock an error response via
MockURLProtocol.mockRequests (returning a ParseError payload and 404 status),
call user.save(options:[], callbackQueue: callbackQueue) and inside the
completion assert DispatchQueue.getSpecific(key: callbackKey) == callbackValue
and that the result is a failure with the expected ParseError; mirror the
existing test's setup (callbackKey, callbackValue, callbackQueue, expectation)
and fulfill/wait the expectation just like in
testSaveAsyncCallbackQueueOnSuccess.