mini now works in Jira

Minitap integrations: GitHub, CI, Slack, tickets and MCP

mini works where your team works.

Findings land in your pull requests, Slack, and your Jira, Linear or Notion tickets.

Every integration, and how far it goes.

Code review and CI

  • GitHub

    Native

    A comment on pull requests to main, a check on every run.

    How far it goes

    Install the Minitap GitHub App once. mini comments on every pull request to your main or release branches, with a box to tick to run the tests, and posts a check named after your app on every run. Comment @mini test to start one, and mini asks on the pull request when it needs context. The check informs by default; turn on Block merge on failing tests and branch protection can require it.

    GitHub docs
  • GitHub Action

    Runs mini from any workflow, signed in with GitHub OIDC.

    How far it goes

    Starts a run from any workflow, signed in with GitHub OIDC. It uploads your build or asks mini to build the commit, picks the browser for web runs (Chrome, Firefox or Microsoft Edge), and can wait for the verdict to hold a release. On a release tag it runs only the tests affected since the previous tag.

    GitHub Action docs
  • CLI, for any CI

    The CLI runs mini from GitLab CI, CircleCI, Jenkins or any CI.

    How far it goes

    The open-source Minitap CLI uploads your .ipa, .apk, .apks or .aab and waits until it is ready, then starts runs and reads every verdict as JSON, with a workspace API key. It runs on real phones where your workspace has them enabled, and downloads each run’s recording, device log and verdicts. GitLab CI, CircleCI, Jenkins, Azure Pipelines and Bitbucket Pipelines run mini through the CLI.

    CLI, for any CI docs
  • GitLab and Bitbucket

    Connect and build

    mini builds and tests your repositories. Gate pipelines through the CLI.

    How far it goes

    Connect a GitLab group, self-hosted included, or a Bitbucket workspace. mini builds from your repositories and keeps the tests in step with your code. Comments and checks on pull requests are GitHub only; gate a pipeline through the CLI.

TestFlight and the App Store

  • TestFlight

    mini runs your TestFlight builds on real iPhones.

    How far it goes

    Add our tester to TestFlight once; Settings walks you through it. Paste a build’s join link and bundle id, and mini runs that build on real iPhones from our managed phone farm, enabled per workspace. Pick any iPhone or a specific model for each test.

  • In-app purchases

    Beta

    mini buys and subscribes in your app. Nobody is charged.

    How far it goes

    mini uses a real iPhone, one per workspace, signed in to its own Sandbox Apple Account, and runs purchases and subscriptions end to end. On iOS simulators, mini buys in a StoreKit test store. Nobody is ever charged. Switch it on per test account.

Where your team talks

  • Slack

    One message per run, and a thread per finding with its clip.

    How far it goes

    mini posts one message per run and edits it as the run goes. Each finding gets a thread with a clip of the failure and three buttons: Acknowledge, Not a bug, Resolved. A scheduled run posts one summary: passed, failed, skipped, new bugs and a link. For test maintenance, mini writes only when it finds an app bug or gets stuck. Start runs with @mini run, and mini asks your team in the channel when it needs context or a test account.

    Slack docs

Tickets and specs

  • Notion

    mini reads your specs and PRDs, and files issues to a database.

    How far it goes

    Connect Notion and mini reads the specs and PRDs your team already wrote, and writes tests from them. Send any finding to a Notion database as a new page, or link it to a page you already have; the finding shows the page’s status.

  • Jira

    Tickets with the recording, and @mini in any comment.

    How far it goes

    mini reads your tickets, their comments, screenshots and test cases for context. Mention @mini in a Jira comment and it runs the scenario, then replies there with the run report, the recording and the scenario. File a ticket from an issue, a UI/UX suggestion or a failed criterion, with the steps to reproduce and the recording, or link a ticket you already have.

  • Linear

    Issues with the steps to reproduce and the recording.

    How far it goes

    mini files a Linear issue from an issue, a UI/UX suggestion or a failed criterion, with the steps to reproduce and the recording attached. Already tracking it? Link the issue you have, and its live status shows beside the finding.

Coding agents

  • MCP server

    Your coding agent reads tests and results, and starts runs.

    How far it goes

    Your coding agent, in Cursor, Claude Code or Windsurf, signs in to mini’s MCP server. It can read and edit tests, test accounts and builds, start runs and read their results.

  • Fix prompts

    Copy a fix prompt from any failed criterion into your agent.

    How far it goes

    Every failed criterion has a Copy fix prompt button: the root cause, the steps to reproduce and a proposed fix, ready for your coding agent. The CLI ships a skill so the agent can run mini itself.

    Fix prompts docs

Hold a release on the verdict.

The Action signs in with GitHub OIDC, waits for the verdict and fails the step on a failing test.

.github/workflows/release.yml
permissions:
  id-token: write

steps:
  - uses: minitap-ai/minitest-trigger@v1
    with:
      app-slug: shop
      wait-for-result: true
      fail-on-failure: true

Good questions.

Does mini block merges?

Not unless you ask it to. mini’s check informs by default. Turn on Block merge on failing tests for an app and the check fails when a test fails, so branch protection can require it. In a release workflow, the GitHub Action can wait for the verdict and fail the step.

Does mini run on every pull request?

No. mini comments on the pull request and waits: a run starts when someone ticks its box, comments @mini test, or your CI calls the Action or the CLI.

Which CI does mini work with?

GitHub Actions natively, through the Minitap GitHub Action. Any other CI, from GitLab CI and CircleCI to Jenkins, Azure Pipelines and Bitbucket Pipelines, runs mini through the open-source CLI with a workspace API key, and reads the verdict as JSON.

Can mini run on a schedule?

Yes. Schedule the whole suite, a tag or the scenarios you pick, on the latest build, a fixed build or a branch. Each run posts one summary to Slack: passed, failed, skipped, new bugs and a link to the run. Runs from your CI work as before.

Do GitLab and Bitbucket get comments and checks?

No. Connect them and mini builds from your repositories and keeps the tests in step with your code. Comments and checks on pull requests are GitHub only, so gate a GitLab or Bitbucket pipeline through the CLI.

How do we get tickets from mini?

Connect Jira, Linear or Notion. From an issue, a UI/UX suggestion or a failed criterion, mini files a ticket with the steps to reproduce and the recording. Already tracking it? Link the ticket you have, and its status shows beside the finding.

Can we run mini from Jira?

Yes. Mention @mini in a Jira comment and mini runs the scenario, then replies there with the run report, the recording and the scenario. mini also reads your tickets, their comments, screenshots and test cases to know what to test.

What does mini get access to?

On GitHub, the repositories you pick when you install the Minitap GitHub App. In Slack, mini joins your public channels, posts each run to the channel you pick, and anything done from Slack runs as the person’s own Minitap account and role. In Jira, Linear and Notion, mini reads what you connect, and writes only the tickets you send and its replies to @mini. The CLI and the MCP server use a workspace API key or your sign-in.

See it in your own tools.

Bring a build. We run mini on it, and the finding lands in your tools.