- 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.
What J2ObjC Is J2ObjC is an open-source command-line tool from Google that translates Java code to Objective-C for the iOS (iPhone/iPad) platform. This tool enables Java code to be part of an iOS application's build, as no editing of the generated files is necessary. The goal is to write an app's non-UI code (such as data access, or application logic) in Java, which is then shared by web apps (using GWT), Android apps, and iOS apps. J2ObjC supports most Java language and runtime features required by client-side application developers, including exceptions, inner and anonymous classes, generic types, threads and reflection. JUnit test translation and execution is also supported. J2ObjC is currently between alpha and beta quality. Several Google projects rely on it, but when new projects first start working with it, they usually find new bugs to be fixed. Apparently every Java developer has a slightly different way of using Java, and the tool hasn't translated all possib...
Comments
Post a Comment