{"id":44121,"date":"2024-07-17T14:52:20","date_gmt":"2024-07-17T18:52:20","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=44121"},"modified":"2024-07-17T14:52:20","modified_gmt":"2024-07-17T18:52:20","slug":"xctest-in-xcode-16","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/07\/17\/xctest-in-xcode-16\/","title":{"rendered":"XCTest in Xcode 16"},"content":{"rendered":"

Jesse Squires<\/a>:<\/p>\n

The first is waitForNonExistence(withTimeout:)<\/code><\/a>, which provides the inverse of the existing waitForExistence(timeout:)<\/code> API. Finally! This is such a welcome change. Often in UI testing it is more semantic to wait for an element to disappear<\/em> rather than appear<\/em> — for example, waiting for a loading indicator or waiting for a UIContentUnavailableView<\/code><\/a> to disappear. Previously, you would have to roll your own implementation or awkwardly use waitForExistence(timeout:)<\/code> and negate the result — both options are cumbersome and inefficient.<\/p>

[…]<\/p>

The second new API is wait(for:toEqual:timeout:)<\/code><\/a>, which waits for a property value of an element to equal a new value. This is useful for when the contents of an existing view should be updated and you want to verify the update happened. The most common use case here is likely for checking the contents of labels, text fields, or text views that change based on state updates or user interaction. Previously, there was not a great way to achieve this without introducing artificial timeouts in your test, or changing the UI element’s .accessibilityIdentifier<\/code><\/a> in your app when its contents updated and then checking for the existence of the new identifier.<\/p><\/blockquote>\n

But he says that the latter currently doesn’t work.<\/p>\n\n

Previously:<\/p>\n