@qawolf/flows/ios defines iOS flows and advanced simulator or device control.
Primary Exports
flow(...)launch(...)deviceexpecttestContextDependencies
Flow Callback Context
All iOS flow callbacks receive:inputssetOutput(...)test(...)
driver.
test(...) can be omitted for simple flows where grouping steps into named sub-steps doesn’t add value. For most flows, wrapping steps in test(...) is recommended — the label appears in your results and makes failures easier to locate.testContextDependencies
testContextDependencies is exported for runner and tooling integration. Flow authors should usually use the public callback parameters above instead of depending on the raw runner dependency list.
Target Model
The current target input model is:- a target directly for the common path
{ target, launch }when startup behavior should be part of the flow
flow(...)
Use flow(...) for iOS authoring.
Behavior from the implementation:
- without launch, the callback receives
inputs,setOutput(...), andtest(...) - with
launch: true, the flow callslaunch()with default iOS startup - with
launch: <options>, the flow callslaunch(options) - when launch is enabled, the callback also receives
driver
launch(...)
launch() starts iOS automation for the active flow and returns:
Launch Shape
Launch Defaults
The current implementation applies these defaults:- when
appis omitted, launch falls back to the runner-provided executable input path and then to installed-app startup throughbundleId respectSystemAlertsdefaults totruesnapshotMaxDepthdefaults to999noResetdefaults tofalse
App Resolution
When your CI pipeline uploads an iOS build, QA Wolf setsRUN_INPUT_PATH to the uploaded file before the flow runs. Omit app in your launch call and QA Wolf will use that path automatically — you only need to provide the bundleId.
When app is provided, the current resolution order is:
app.pathapp.envapp.url
app is omitted, launch falls back to RUN_INPUT_PATH.
Relative paths are resolved against RUN_INPUTS_EXECUTABLES_DIR when that environment variable is present.
Explicit app source examples:
RUN_INPUT_PATH fallback example:
If
app is present but does not resolve to a value, launch does not fall back to RUN_INPUT_PATH.device
device is a runtime proxy over the iOS simulator or device API. Use it for device-level operations — such as installing configuration profiles, simulating sensors, or managing device state — that sit outside app UI interactions. Use driver for interacting with the app itself.
Example:
expect
The exported expect value is a type-safe stub in package code and is replaced by the runner during execution.
Example: