- 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.
Automatic Reference Counting (ARC) largely removes the burden of manual memory management, not to mention the chore of tracking down bugs caused by leaking or over-released objects! Despite its awesomeness, ARC does not let you ignore memory management altogether. This post covers the following key aspects of ARC to help you get up and running quickly. Reference Counted Memory: Quick Revision How Automatic Reference Counting Works Enabling ARC in Your Project New Rules Enforced by ARC ARC Qualifiers – Declared Properties ARC Qualifiers – Regular Variables Migrating Existing Projects to ARC Including Code that is not ARC Compliant Should I Use ARC? The Long Weekend Website
Comments
Post a Comment