Welcome and let’s explore together
While investigating some memory leak issue, I found out that if I po an object before using Memory Graph, that object would stay in memory forever, and Memory Graph would show something like NSKeyValueDependencyInfo as an owner of the object. A leak will also happen when using p or expression. See for more details: https://github.com/kastiglione/swift_po.
Last time I encountered this issue, it was hard to find the reason. We don’t know much about what actually UI Tests system waits for in such cases. There are rumours over internet that activity on main thread is what it looks for, but it’s not always the case. Let’s go over few tips thatContinue reading “Xcode UI Tests: infinite “wait for app to idle””
TL;DR Use snapshot() method of XCUIElement in order to get consistent element information. Asynchronous nature of UI Tests Tests happen in a separate process, Test Runner, that doesn’t have access to actual views of our App. Runner talks to App using some special communication channel, probably inter-process mechanism. Our code dispatches requests to this mechanism,Continue reading “UI Tests are asynchronous and dynamic. Issues and tips.”
The issue I am going to talk about is relevant to anyone who uses Core Data. It is an “invisible” issue that may show up so rarely that it’s almost impossible to debug. It is only catchable by repeated automated tests. Let’s take a look at the piece of code that has single perform(_:) whichContinue reading “Your Core Data fetches may return unexpected results, or why you should use Query Generations”
Something went wrong. Please refresh the page and/or try again.
Follow My Blog
Get new content delivered directly to your inbox.