Skip to main content
Workbench, under Test suite in the app sidebar, is where changes to your suite wait before they go live. Mini and your team propose changes there, Mini proves them on a device, and nothing reaches your runs until a change is merged. It has two tabs: Proposed changes and CI & Maintenance.

​
Proposed changes

Each proposed change is a draft: a set of scenario changes plus a conversation with Mini about them. Your suite keeps running the current scenarios until the draft is merged.
A Workbench draft, Ready to merge: one added scenario proven on a device, its criteria, Merge into suite, and Mini's conversation on the right

A draft: the changed scenarios on the left, Mini's conversation on the right.

​
Who opens a draft

A teammate can open any draft and pick up the conversation where you left it. Coding agents open and follow drafts with minitest draft (see From the CLI).

​
The Open list

The Open tab sorts drafts by what they wait on: The count on Workbench in the sidebar only counts drafts that need you or are ready to merge. History lists the drafts that were merged or discarded.

​
From change to merge

1

Mini writes the change

Mini adds, edits or removes scenarios in the draft, marked + ADDED, ~ EDITED and − REMOVED. When the flow is new to it, Mini first explores that part of the app on a device. A draft that imports test cases also gets a Source cases tab: see Import your existing tests.
2

Mini checks it on a device

Click Check, or turn on Auto-check to check changed scenarios as soon as Mini stops writing. Mini runs each changed scenario on every platform your app ships, against your latest build, the way a run would. When a scenario fails because it asks for the wrong thing, Mini fixes it and checks again. When the app looks at fault, Mini says so in the chat.
3

You merge

Every scenario has to be proven before the draft can merge. Then click Merge into suite: your next run uses the new versions.
While a draft waits for a build, Mini checks it as soon as one is ready. Any build you upload, from the Workbench, the CLI or when you start a run, is checked against the drafts waiting for it.

​
When something needs you

  • A check failed and Mini is wrong. Click Not a bug on the scenario and say what Mini got wrong. Mini fixes the scenario instead and runs it again, and it doesn’t use up a fix attempt.
  • Mini asks a question. Answer it in the chat. Your suite keeps running the current scenarios meanwhile.
  • You step into a maintenance draft. Once you write in a draft Mini’s maintenance opened, Mini stops checking and merging it on its own. Turn Auto-check back on, or click Check when you’re done.
  • One scenario doesn’t belong. Open its menu for Check this scenario, Ask Mini about this scenario or Remove from draft….
Discard draft… drops Mini’s changes and leaves your suite exactly as it is. A merged draft can be undone from History with Revert: every scenario it changed goes back to how it was, scenarios it added are removed and scenarios it removed come back. Only admins can revert a draft. Drafts you open from the dashboard always wait for you to merge. Mini’s maintenance drafts merge on their own, except when they remove a scenario, conflict with the live suite, have a failing check, or found what looks like a bug in your app.

​
CI & Maintenance

The second tab sets how Mini maintains your suite and, once the app is linked to GitHub, how it handles your pull requests and releases. Without GitHub, the tab is called Maintenance and only shows Autonomy.
Workbench, CI & Maintenance tab: Block merge on failing tests, Release tags, Release branches, and Fix test scenarios without asking

Workbench → CI & Maintenance.

How the pull request comment, the check and release runs work is covered in Pull request checks.

​
From the CLI

Your coding agent can open a draft, talk to Mini, and merge the proven change with the same rules:
draft link-pr <draft-id> <pr-number> proves a draft on an open pull request’s head commit, before the pull request merges. See Coding agents to set up the CLI.

​
Next steps

Mini maintains your suite

What Mini’s maintenance drafts cover, and when it opens them.

Pull request checks

The comment, the check and the merge gate on GitHub.

Ask Mini

Ask for a change in plain language.

Import your existing tests

Turn your test plan into scenarios, case IDs included.