Regression Studio
Sign inStart free

For iOS teams on Xcode 16+

iOS regression tests your whole team can write.

Describe a user journey in a few lines of YAML. Regression Studio turns it into XCUITest, runs it on a simulator from your Mac or CI, and shows every run with screenshots, video and the exact step that failed.

Start free See how it works

Free plan included. No credit card needed.

cases/search_and_play.yaml
id: search_and_play
name: Search for content and start playback
include:
  -  flows/login.yaml
steps:
  - tap: { label: Search, as: button }
  - type: { into: searchField, text: "Breaking Bad" }
  - tap: { id: searchResult_0, screenshot: after }
  - assertVisible: { element: playerView, timeout: 15 }
Run on main · 2 min ago
2 of 3 scenarios passed
Failed
  • login_success
  • browse_catalog
  • search_and_playStep 4: playerView didn't appear within 15 s

How it works

From a YAML file to a reviewed run in three commands

Install the CLI with pipx install regression-studio. It needs a Mac with Xcode and nothing added to your app beyond accessibility identifiers.

  1. 1

    Write cases in YAML

    Tap, type, swipe and assert by accessibility identifier. Share login and other flows between cases with include.

    regstudio init regression
  2. 2

    Run on a simulator

    The CLI generates XCUITest, builds and runs it against your simulator build, locally or on any macOS CI runner.

    regstudio run --app YourApp.app
  3. 3

    Publish and review

    Add --publish and the run shows up for your whole team, with history, screenshots and video for every scenario.

    regstudio run --app YourApp.app --publish ios-app

Features

Everything you need to trust a release

One place for your regression suite, its runs and the evidence behind each result.

Tests without Swift

QA, product and developers write the same YAML. The web editor checks every case against the schema and autocompletes steps as you type.

Screenshots and video

Capture before or after any step, or record the whole scenario. Click a step to see its screenshot and jump the video to that moment.

The failing step, not a log

Each scenario shows as a flow of steps with timings, so you see where it broke and what the screen looked like.

Deterministic network

Optionally serve API responses from fixtures per scenario through a local proxy, so runs don't depend on staging data.

Built for CI

One command in GitHub Actions or any macOS runner. Store an API key as REGSTUDIO_TOKEN and every run links back to its build.

Ready for teams

Organizations with projects, roles from viewer to owner, invitations, API keys for CI and an activity log of who changed what.

Pricing

Start free, upgrade when your suite grows

Free

$0/month

100 runs a month, results kept 7 days

Team

$49/month

2,000 runs a month, results kept 90 days

Business

$199/month

Unlimited runs, results kept 365 days

Compare plans

Ship your next release with a green run

Create an account, publish your first run in minutes, and invite your team.

Start freeCompare plans