Changelog

What’s new in mini.

Every release of mini, newest first.

Read the docs Follow Minitap on LinkedIn

miniTest v1.7.11: Camera mocking, Turkish, and a map of your app

Test camera features on cloud devices

Mini can now feed an image to the camera on cloud Android and iOS devices, so flows like scanning a QR code or a document can be tested end to end.

No physical setup: the camera sees exactly the image your scenario needs, every time.

Android and iOS: works on both cloud platforms.

miniTest speaks Turkish

The app is now available in Turkish, and you can choose the language for yourself and your workspace.

Language preferences: pick your interface language, with a default for the whole workspace.

Results in your app's language: Mini writes test results in the language your app uses, and keeps it across retries.

A map of your app in the Testing sidebar

A new Map tab shows the screens Mini discovered while exploring your app and how they connect.

See coverage at a glance: spot the areas of your app Mini already knows.

Jump from chat: screens Mini mentions in chat and in your inbox now open directly.

Smaller improvements

New sign-in and sign-up: a cleaner design, and every sign-in error is now explained clearly.

Sharper visual checks: Mini can now judge how your screens look at full resolution.

miniTest v1.7.10: Scenario tags, a new run launcher, and every action in your recordings

Organize and run your tests with tags

Scenario categories are now tags: give a scenario as many as you need, and Mini tags new scenarios for you.

Run by tag: pick a tag and launch every scenario that carries it, from the app or with the CLI.

My tags: pin the tags you care about and Runs, Issues and the run launcher open on them by default.

Filter everywhere: narrow runs, issues, UI/UX suggestions down to a tag in one click, and create or rename tags from Manage tags.

A simpler run launcher

Starting a run now fits in a single step: choose your scenarios and see exactly where each one will run before you launch.

Scenarios first: select what to test, then review a clear table of the devices and platforms each scenario will use.

Several devices at once: filter and pick multiple devices for the same run.

Mix your builds: build one platform from a commit while reusing an uploaded build for the other.

See every action Mini takes in a run

Run recordings now show what Mini did, step by step, so you understand a result without rewatching the whole video.

Actions tab: a list of Mini's taps, typing, swipes, rotations and location changes. Click one to jump to that moment in the video.

Backend calls on the timeline: when Mini calls your backend during a test, the call appears on the recording. Hover it to see the request and response, with sensitive data redacted.

From the CLI too: download a run's recording together with its timed verdicts and actions.

Smaller improvements

Clearer skipped checks: skipped criteria no longer show up as passed on the recording.

Reruns that stay put: canceling a run from the CLI now works on every platform, and long CLI sessions no longer drop when your login refreshes.

miniTest v1.7.9: Drafts you can review, guided setup, and Jira

A guided first-time setup

Step by step: connect your repository, Slack and your tools, then let the setup assistant finish the job.

Jira joins Mini's context

Connect Jira and Mini reads your tickets to understand what to test, alongside your other sources.

Available everywhere: add Jira during onboarding, from the setup assistant, or later from Mini's context.

Read only: Mini reads your entire Jira tickets content including comments, screenshots etc.

Smaller improvements

API request inspection: web and mobile web runs can now look at the network requests your app makes.

Steadier test runs: more reliable typing into web forms on Android, mocked GPS on more devices, and email sign-ins that recover from network hiccups.

miniTest v1.7.8: TestFlight on real iPhones, persona test cards, and a smoother setup

Test your TestFlight builds on real iPhones

Workspaces with physical devices can now run their iOS apps on real iPhones straight from TestFlight, and choose exactly which phone runs each test.

Guided TestFlight setup: Settings > General walks you through adding our tester to TestFlight, with a clear Action needed marker until it is done.

Add TestFlight builds in seconds: paste the join link and bundle id, and the build appears in your builds list named after its bundle id.

Pick the phone: the run dialog lets you choose a cloud device, any real iPhone, or a specific model, with live availability for each.

Test cards for your personas

Checkout flows are now easy to test: give a persona a sandbox payment card and Mini uses it whenever a scenario reaches payment.

Right in the persona editor: add a card number, expiry, CVC, holder name and postal code, all optional, and edit or remove it anytime.

Stored securely: the card is encrypted at rest and never leaks into run reports.

From the CLI too: set, update or clear a persona's test card from the miniTest CLI.

Smaller improvements

Clearer screen maps: a path where the app was relaunched is now labeled App launch, and screens reached after a relaunch connect back to the start of the map.

miniTest v1.7.7: Guided setup, and a browsable phone fleet

Guided setup, from empty app to first regression

Setting up a new app is now a guided conversation with Mini that ends with your first regression already running.

Bring the test cases you already have: attach a zip, CSV, Markdown or PDF during setup and Mini reads them straight into your suite.

Watch Mini explore: the exploration map lays your screens out by depth and draws every path between them, with a live device view while Mini walks the app.

Approve and go: approving your scenarios finishes onboarding and starts the first regression, and your app stays fully usable while that run happens.

Browse the phone fleet and request devices

See which real phones are available to your workspace, and ask for the models you are missing.

A live inventory: see every phone model in the fleet, the OS versions it runs, and how many are free right now.

Request the devices you need: ask for a platform, model, OS version and quantity, then follow each request through to fulfilment.

Smaller improvements

Steadier device connections: a dropped connection to a phone is retried transparently instead of failing the command outright.

Clearer accessibility results: a criterion still under review no longer reads as not applicable, and each element is counted once at its strongest status.

Accessibility, explained: a new guide covers what an accessibility run produces and how to read it.