You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apple introduced a new UI Testing feature starting from Xcode 7 that is, quoting Will Turner on stage at the WWDC, a huge expansion of the testing technology in the developer tools. The framework is easy to use and the integration with the IDE is great however there is a major problem with the way tests are launched. Testing code runs as a separate process which prevents to directly share data with the app under test making it hard to do things like dynamically inject data or stub network calls.
SBTUITestTunnel extends UI testing functionality allowing to dynamically:
stub network calls
download/upload files from/to the app's sandbox
monitor network calls
rewrite network calls
block cookies
interact with NSUserDefaults
define custom blocks of codes executed in the application target
fine grain fast-scrolling in table/collection/scroll views
CLLocationManager stubbing
UNUserNotificationCenter stubbing
The library supports concurrent parallel testing, so multiple Simulators can be used at once.
The library consists of two separated components which communicate with each other, one to be instantiate in the application's target and the other in the testing target.
Should I use this?
SBTUITestTunnel is intended to extend Apple's XCTest framework, not to replace it. It all boils down to a single subclass of XCUIApplication which comes with the additional features listed above, so it is very easy to integrate with your existing testing code.
Documentation
Installation: Describes how to install the library
Setup: Describes how to integrate the library in your code