You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add walkthrough comments explaining log-vs-failure for nil records
Explains why post-delete SOQL/SOSL verification uses NSLog instead of
XCTAssertNotNil: delete already asserted success, queryAll verifies
recycle bin, and these steps only check index consistency. A hard
assertion caused ~1-in-10 CI flakes.
XCTAssertEqual((int)[records count], 0, @"expected no result");
662
667
} else {
663
668
NSLog(@"[testCreateQuerySearchDelete] SOQL poll never got a valid response — server may have been briefly unreachable during post-delete verification");
664
669
}
665
-
670
+
666
671
// check the deleted object is here
667
672
request = [[SFRestAPI sharedInstance] requestForQueryAll:[NSStringstringWithFormat:@"select Id, FirstName from Contact where LastName='%@'", lastName] apiVersion:kSFRestDefaultAPIVersion];
0 commit comments