Flow file & selectors

A flow is one YAML file. Top-level keys:

Key	Summary
appId	Default app under test
commands	The ordered list of steps
tags	Tags for filtering
onFlowStart	Setup steps (run before commands)
onFlowComplete	Teardown steps (always run after)
env	Flow variables, used as ${VAR} (config env / .env / -e override them)
params	Declared inputs: description, required, default, options — callers pass them via runFlow params: or -e
device	none = pure-API flow: no device is resolved or booted; only request/scripts/value asserts allowed

appId: https://staging.example.com
tags: [smoke]
commands:
  - tapOn: "Log in"
  - inputText: "hello"
  - assertVisible: "Welcome"

Selectors

Commands that target an element take a bare string (matched against visible text) or an object with any of:

• text
• id
• regex
• index
• enabled
• checked
• focused
• point

- tapOn:
    id: submit-button
- assertVisible:
    text: "Order placed"
    index: 0