Skip to main content
A test suite is easy to write and hard to keep honest. Your app keeps moving, and the suite has to move with it. Mini’s self-maintenance is what keeps the two in sync. Mini reads your codebase, generates the first version of the suite, and keeps it current as you ship. Add a feature and it drafts a story for it. Remove one and the story retires. Reshape a screen and it rewrites the criteria to match.
Automatic self-maintenance needs the GitHub integration. The background flow reads your repo to detect changes on the default branch, so without the GitHub integration active and pointed at the right repo, Mini has nothing to watch. No GitHub? Run maintenance yourself from the CLI. See Maintenance from the CLI.

​
What it covers

Microscopic drift

A renamed button, a tweaked label, a reordered form. The story stays; criteria are rewritten to match what’s on screen now.

Macroscopic drift

A whole feature removed, a new journey shipped. Stories are added or retired.

Connective tissue

Dependencies between stories get wired automatically. Existing profiles get linked to the journeys that need them.

​
How it works

Mini watches what lands on the default branch (main in most cases). When the diff is meaningful, it updates the suite in the background: it drafts new stories, retires stale ones, and rewrites criteria to match the new UI. You don’t trigger it, and you don’t review every change. You just keep shipping.

​
What stays manual

Two things Mini can’t infer from code alone:

New profiles

If a new journey needs a new identity (a Pro user to test a paywall, an Admin for a settings screen), you’ll be prompted to provide the credentials. Existing profiles get linked automatically.

Device files

Photos to upload, PDFs to attach, audio to play back. Anything that lives outside your repo, you attach by hand.
Both can be done from the dashboard, your IDE, or Slack.

​
Maintenance from the CLI

If you’d rather not connect GitHub, run maintenance on demand from your app repository with the minitest maintenance command group. Your own AI coding agent reads the local diff and drafts the criteria edits; the CLI sends only those proposed edits and the local commit SHA, so your code never leaves your machine.
The agent opens a run, declares affected stories, and posts proposed changes to the Release queue. Review them in the dashboard or apply them straight away:
See the maintenance command reference for the full workflow.