- 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.
There are two things you need to do. First, check to see if TestFlight is installed. Then create a new link to your app. NSURL *customAppURL = [NSURL URLWithString:@"itms-beta://"]; if ([[UIApplication sharedApplication] canOpenURL:customAppURL]) { // TestFlight is installed // Special link that includes the app's Apple ID customAppURL = [NSURL URLWithString:@"https://beta.itunes.apple.com/v1/app/978489855"]; [[UIApplication sharedApplication] openURL:customAppURL]; } This special https://beta.itunes.apple.com URL will be opened directly in TestFlight. Finally, if you are using iOS 9 (or later), you need to make an addition to your Info.plist to get the canOpenURL: method to work. If your app is linked on or after iOS 9.0, you must declare the URL schemes you want to pass to this method. Do this by using the LSApplicationQueriesSchemes array in your Xcode project’s Info.plist file. For each URL scheme you wan...
Comments
Post a Comment