Automation scenarios & schedules
Automate real iPhones with scenarios and schedules
A HelmSwarm scenario is a list of steps — tap, type, wait for an element, assert text, branch, loop — that runs on real iPhones. Build it in a visual editor, run it on one device or a whole fleet, and schedule it so your regression suite runs while you sleep.
Automation & schedules in detail
Steps that read like a test plan
Scenarios are made of steps you pick from a list and fill in. The editor covers:
- InteractTap, long-press, swipe, drag, type, press home, open or close apps, open URLs.
- Find elementsTap or type into elements by accessibility ID, NSPredicate, XPath or class chain instead of fixed coordinates.
- Check resultsWait for an element, assert it's visible, assert its text, and take screenshots for the run report.
- Control flowIf-visible branches, loops, variables and reusable sub-scenarios keep long flows readable.
Secrets stay out of your steps
Test-account passwords and tokens live in an encrypted vault and are referenced by name — ${secret.email} — so scenarios can be shared and exported without exposing credentials.
Run on the right devices
Pick devices by hand or let HelmSwarm suggest them by iOS version and tags, then run in parallel or sequentially. Each run records per-device results and screenshots; open a run to see which step failed on which iPhone, or compare two runs to spot what changed.
Schedules and reports
Attach a cron schedule to any scenario and check the next run times before you save. Run results export as JUnit XML for CI dashboards, and analytics highlight flaky scenarios that pass and fail without code changes.
Start from a recording or a sentence
Record steps while you control a device, or describe the flow in plain English and let AI draft the steps for you to review. Scenarios import and export as YAML for version control.
Automation & schedules: common questions
Do I need to write code to automate an iPhone?
No. Scenarios are built in a visual editor from ready-made steps. If you prefer text, scenarios import and export as YAML.
Can scenarios use element locators instead of coordinates?
Yes. Steps can target elements by accessibility ID, NSPredicate, XPath or class chain, which keeps scenarios working across screen sizes.
Which time zone do schedules use?
Schedules are written as cron expressions and run in UTC. The editor previews the next run times so you can check them before saving.
Can I run Appium or XCUITest suites I already have?
HelmSwarm runs its own scenarios through WebDriverAgent; it doesn't currently host external Appium or XCUITest suites. Many teams rebuild their critical flows as HelmSwarm scenarios and keep unit tests in their existing pipeline.
More HelmSwarm features
Live device control
Live screen streaming with taps, swipes, pinch, typing, hardware buttons, apps and URLs.
AI Command
Describe a task in plain English; review the steps, pick devices, confirm anything risky.
Multi-device mirroring
Side-by-side view and mirror mode: one tap or swipe, repeated on every selected iPhone.
Put real iPhones under one helm
Tell us how many devices you need and how you test. We'll confirm compatibility, pricing and the next steps by email.