- Generic approach to iOS UI Tests in Swift
- Page object concept
- WWDC 2017 What's New in Testing
- Xcode Automated UI Tests & NSUserDefaults
- The solution I found was to write to the launchArguments property of my XCUIApplication instance in my test class, and then read that parameter in my AppDelegate class.
- XcodeUITestingExperiments
- NetworkStubbingExperiment
- FileSystemManipulation
- SystemLogQuery
- Lightweight IPC with the Darwin notification center
-
- Disabling animations
- Page objects
- Assert helpers
- Network data stubbing with Wire Mock
- Using data from mocks in tests
- Instrumentation Testing Robots
- Libraries like Espresso allow UI tests to have stable interactions with your app, but without discipline these tests can become hard to manage and require frequent updating. In this talk Jake will cover how the so-called robot pattern allows you to create stable, readable, and maintainable tests with the aid of Kotlin’s language features.
- It’s true that you can’t manually manage your application objects’ reference count in iOS applications. There are, however, things you can do to free up memory – the big ones in the 1.x product are closing windows (which releases all UI resources associated with the window) and setting references to a proxy object (like one returned by Ti.UI.createXXX) to null, which will release the resources associated with that object. Why you should stay away from Titanium
Comments
Post a Comment