fa3c2bc959
Summary: Some log readers care about the substring rather than the entire line, so fetching an entire line is optional. Reviewed By: nqmtuan, marekcirkos Differential Revision: D3035471 fb-gh-sync-id: d7727817f650a4c87dbfff59be6b7fe6136693de shipit-source-id: d7727817f650a4c87dbfff59be6b7fe6136693de |
||
---|---|---|
FBControlCore | ||
FBControlCoreTests | ||
FBSimulatorControl | ||
FBSimulatorControl.xcodeproj | ||
FBSimulatorControlTests | ||
Help | ||
PrivateHeaders | ||
Shims | ||
fbsimctl | ||
.gitignore | ||
.travis.yml | ||
CONTRIBUTING | ||
LICENSE | ||
PATENTS | ||
README.md | ||
build.sh |
README.md
FBSimulatorControl
A Mac OS X library for managing, booting and interacting with multiple iOS Simulators simultaneously.
Features
- Enables 'Multisim' for iOS: Booting of multiple Simulators on the same host OS.
- Runs independently of Xcode and
xcodebuild
. Uses the toolchain defined byxcode-select
. - Boots iPhone & iPad Simulators for iOS 7, 8 & 9.
- Boots watchOS Simulators since watchOS 2.0.
- Boots tvOS Simulators since tvOS 9.0.
- Launches both 'Agent' and 'Application' processes, with Arguments and Environment.
- Can boot Simulators via Xcode's
Simulator.app
or by launching 'Directly' inCoreSimulator
. - 'Direct Launch' supports video recording, screenshot fetching & interfacing with the
SimulatorBridge
. - 'Diagnostic' API for fetching System, App & Crash logs as well as Screenshots & Video.
- An 'Event Bus' that exposes the details of a Simulator's lifecycle including Applications, Agents & the Simulator itself.
- Persistent and Queryable history of all events in Simulator's lifecycle.
NSNotification
s interface for the 'Event Bus'.- Stateless by Default: Knowledge the current state of Simulators can be re-built when
FBSimulatorControl
is launched. - BFFs with
WebDriverAgent
. - No external dependencies.
About
The original use-case for FBSimulatorControl
was to boot Simulators to run End-to-End tests with WebDriverAgent
. As FBSimulatorControl
is a Mac OS X framework, it can be linked to from inside any Mac OS Library, Application, or xctest
target. There may be additional use-cases that you may find beyond UI Test Automation.
FBSimulatorControl
works by linking with the private DVTFoundation
, CoreSimulator
and DVTiPhoneSimulatorRemoteClient
frameworks that are present inside the Xcode bundle. Doing this allows FBSimulatorControl
to talk directly to the same APIs that Xcode and simctl
do. This, combined with launching the Simulator binaries directly, means that multiple Simulators can be launched simultaneously. Test targets can be made that don't depend on any Application targets, or that launch multiple Application targets. This enables running against pre-built and archived Application binaries, rather than a binary that is built by a Test Target.
As FBSimulatorControl
nears a stable version, the API may change but can be considered mostly stable.
Installation
The FBSimulatorControl.xcodeproj
will build the FBSimulatorControl.framework
and the FBSimulatorControlTests.xctest
bundles without any additional dependencies. The Project File is checked into the repo and the Framework can be build from this project.
Once you build the FBSimulatorControl.framework
, it can be linked like any other 3rd-party Framework for your project:
- Add
FBSimulatorControl.framework
to the Target's 'Link Binary With Libraries' build phase. - Ensure that
FBSimulatorControl
is copied into the Target's bundle (if your Target is an Application or Framework) or a path relative to the Executable if your project does not have a bundle.
Usage
In order to support different Xcode versions and system environments, FBSimulatorControl
weakly links against Xcode's Private Frameworks and load these Frameworks when they are needed. FBSimulatorControl
will link against the version of Xcode that you have set with xcode-select
. The Xcode version can be overridden by setting the DEVELOPER_DIR
environment variable in the process that links with FBSimulatorControl
.
Since the Frameworks upon which FBSimulatorControl
depends are loaded laziliy, they must be loaded before using the Framework. Any of the FBSimulatorControl
classes that have this runtime dependency will load these Private Frameworks when they are used for the first time.
The tests should provide you with some basic guidance for using the API. FBSimulatorControl
has an umbrella that can be imported to give access to the entire API.
For a high level overview:
FBSimulatorControl
is the Principal Class. It is the first object that you should create with+[FBSimulatorControl withConfiguration:error:]
. It creates aFBSimulatorPool
upon creation.FBSimulatorSet
wrapsSimDeviceSet
and provides a resiliant CRUD API for Deleting, Creating and Erasing Simulators.FBSimulatorPool
builds onFBSimulatorSet
by providing an 'Allocation' API that allows Simulators to be reserved and re-used within the Framework.FBSimulator
is a reference type that represents an individual Simulator. It has a number of convenience methods for accessing information about a Simulator.FBSimulatorInteraction
and it's categories forms the API of possible ways of interacting with a Simulator. These range from booting Simulators, installing & running Applications, uploading photos & videos and more.FBSimulatorHistory
is a record of all the events that happen to a Simulator. It can be queried in a variety of ways and serialized to file.FBSimulatorDiagnositcs
is a facade around available diagnostics for a Simulator. It fetches static logs such as the System Log on-demand and receives new logs from components such asFBFramebufferVideo
.- Configuration objects:
FBApplicationLaunchConfiguration
,FBAgentLaunchConfiguration
,FBSimulatorApplication
,FBSimulatorControlConfiguration
,FBSimulatorConfiguration
&FBSimulatorLaunchConfiguration
.
To launch Safari on an iPhone 5, you can use the following:
// Create a suitable configuration for FBSimulatorControl.
// This Configuration will ensure that no other Simulators are running.
FBSimulatorManagementOptions managementOptions = FBSimulatorManagementOptionsKillSpuriousSimulatorsOnFirstStart;
FBSimulatorControlConfiguration *controlConfiguration = [FBSimulatorControlConfiguration
configurationWithDeviceSetPath:nil
options:managementOptions];
// The principal class, must be retained as long as the Framework is used.
// If there is something wrong with the environment and error will be returned.
NSError *error = nil;
FBSimulatorControl *control = [FBSimulatorControl withConfiguration:controlConfiguration error:&error];
// Create the Configuration for the Allocation & Creation of a Simulator.
// When a Simulator is Allocated, a Simulator matching the given configuration is reused if one is available
// Otherwise a Simulator with the provided configuration will be created.
// The Simulator returned as a result will be shutdown and erased.
FBSimulatorConfiguration *simulatorConfiguration = FBSimulatorConfiguration.iPhone5;
FBSimulatorAllocationOptions allocationOptions = FBSimulatorAllocationOptionsCreate | FBSimulatorAllocationOptionsReuse | FBSimulatorAllocationOptionsEraseOnAllocate;
// Obtain a Simulator from the Principal Class. If anything goes wrong, nil will be returned along with a descriptive error.
FBSimulator *simulator = [control obtainSimulatorWithConfiguration:simulatorConfiguration options:allocationOptions error:&error];
// Build a Launch Configuration.
FBApplicationLaunchConfiguration *appLaunch = [FBApplicationLaunchConfiguration
configurationWithApplication:[FBSimulatorApplication systemApplicationNamed:@"MobileSafari" error:&error]
arguments:@[]
environment:@{}];
// System Applications can be launched directly since they are already 'installed' in the Simulator.
// Applications provided by the user must be installed after Booting with `installApplication:`.
BOOL success = [[[simulator.interact
bootSimulator]
launchApplication:appLaunch]
perform:&error];
FBSimulatorControl
currently has two ways of launching Simulators that have tradeoffs for different use cases. Since Xcode 7.2, both these methods can be used:
Multisim
The CoreSimulator
Framework that is used by the Simulator.app
as well as Playgrounds & Interface Builder has long had the concept of custom 'Device Sets' which contain created Simulators. Multiple Device Sets can be used on the same host and are an effective way of ensuring that multiple processes using CoreSimulator
don't collide into each other. 'Device Sets' are also beneficial for an automation use-case, as using a different set other than the 'Default' will ensure that these Simulators aren't polluted.
CoreSimulator
itself is also capable of running multiple Simulators on the same host concurrently. You can see this for yourself by using the simctl
commandline. Booting Simulators this way can be of somewhat limited utility without the output of the screen. FBSimulatorControl
solves this problem in two different ways:
Launching via Simulator.app
Simulator.app
is the Mac OS X Application bundle with Xcode that you are probably familiar with for viewing and interacting with a Simulator. This Mac Application is the part of the Xcode Toolchain that you will be used to.
FBSimulatorControl
can launch the Application Excutable directly, thereby allowing specific Simulators to be booted by UDID and Device Set. This can be done by overriding the Simulator.app
s NSUserDefaults
by passing them as Arguments to the Application Process. Once the Simulator has booted, it can be interacted with via CoreSimulator
with commands such as installing Apps and launch executables.
However, this mode of operation does limit the amount that FBSimulatorControl
can manipulate the Simulator, once the Simulator.app
process has been launched. In particular it's not possible to execute custom code inside the Simulator Application process, which means that it's not possible to get video frames that the booted simulator passes back to the Simulator.app
process.
Direct Launch
FBSimulatorControl
also supports 'Direct Launching'. This means that the Simulator is booted from the FBSimulatorControl
Framework. This gives increasing control over the operation of the Simulator, including fetching frames from the Framebuffer. This means that pixel-perfect videos and screenshots can be constructed from the Framebuffer. In addition, FBSimulatorControl
can communicate to the SimulatorBridge
process running on the Simulator over XPC.
Direct Launching does not currently support manipulation of the UI within the Simulator, so is much better suited to a use-case where the UI is manipulated by other means.
fbsimctl
fbsimctl
is a Command Line Interface for FBSimulatorControl
API calls, so FBSimulatorControl
functionality can be used without the need to integrate with the Framework. It is currently under development. As fbsimctl
is under active development, the User Interface will be prone to change.
Contributing
See the CONTRIBUTING file for how to help out. There's plenty to work on the issues!
License
FBSimulatorControl
is BSD-licensed. We also provide an additional patent grant.