Minitap Trigger Tests Action

A GitHub Action that triggers your Minitest suite from your CI workflow. It authenticates via GitHub OIDC, uploads your build artifacts, and kicks off test execution — all fire-and-forget. Results are reported back to your PR via GitHub Check Runs.

Quick Start

name: Run Minitest Suite
on:
  push:
    tags: ['v*']

permissions:
  id-token: write # Required for OIDC authentication

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6

      # Build your app for simulators/emulators (your build steps here)

      - uses: minitap-ai/minitest-trigger@v1
        with:
          app-slug: my-app
          ios-build-path: ./build/MyApp.app
          android-build-path: ./build/app-debug.apk

Inputs

Input	Required	Default	Description
app-slug	Yes	—	The Minitest app slug to test
ios-build-path	*	—	Path to the iOS simulator build (.app directory or .ipa file)
android-build-path	*	—	Path to the Android emulator build (.apk, must target x86-64)
flow-types	No	—	Comma-separated flow types to run (e.g., login,checkout)
tenant-id	No	—	Tenant ID (required if repo is linked to multiple tenants)
api-url	No	https://testing-service.app.minitap.ai	Override API base URL

* At least one of ios-build-path or android-build-path is required.

Outputs

Output	Description
batch-id	The ID of the triggered test batch
status	Initial status of the triggered batch

How It Works

1. Validate Builds — Checks that your build artifacts meet the requirements (see below)
2. OIDC Authentication — Requests a GitHub OIDC token scoped to the Minitap API. No secrets to manage!
3. Upload Builds — Uploads your simulator/emulator builds to Minitap (.app bundles are automatically packaged into .ipa)
4. Trigger Run — Calls the Minitap CI API with your configuration
5. Fire & Forget — The action exits immediately. Results are reported back via GitHub Check Runs

Build Requirements

You must provide at least one build artifact. Minitap runs your app on simulators and emulators, so builds must target those environments.

iOS

Provide a simulator .app bundle or a .ipa file.

Format	Description
.app	Simulator bundle directory (automatically packaged into .ipa)
.ipa	IPA file (uploaded as-is)

To build for the iOS Simulator with xcodebuild:

xcodebuild build \
  -scheme MyApp \
  -sdk iphonesimulator \
  -configuration Debug \
  -derivedDataPath ./build
# Output: ./build/Build/Products/Debug-iphonesimulator/MyApp.app

Android

Provide a .apk file built for x86-64 emulators. The action inspects the APK and verifies it contains native libraries for the x86_64 architecture (lib/x86_64/).

To build an x86-64 debug APK with Gradle, configure your app's build.gradle:

// app/build.gradle
android {
  defaultConfig {
    ndk { abiFilters 'x86_64' }
  }
}

Then build:

./gradlew assembleDebug
# Output: app/build/outputs/apk/debug/app-debug.apk

Note: If your APK only contains arm64-v8a or armeabi-v7a libraries, the action will fail with a clear error telling you which architectures were found.

Examples

iOS only

- uses: minitap-ai/minitest-trigger@v1
  with:
    app-slug: my-app
    ios-build-path: ./build/Build/Products/Debug-iphonesimulator/MyApp.app

Android only

- uses: minitap-ai/minitest-trigger@v1
  with:
    app-slug: my-app
    android-build-path: ./app/build/outputs/apk/debug/app-debug.apk

Both platforms with specific flow types

- uses: minitap-ai/minitest-trigger@v1
  with:
    app-slug: my-app
    ios-build-path: ./build/MyApp.ipa
    android-build-path: ./build/app-debug.apk
    flow-types: login,checkout,onboarding

Multi-tenant setup

- uses: minitap-ai/minitest-trigger@v1
  with:
    app-slug: my-app
    android-build-path: ./build/app-debug.apk
    tenant-id: tenant_abc123

Prerequisites

Your workflow must have the id-token: write permission for OIDC authentication to work:

permissions:
  id-token: write

Development

# Install dependencies
npm install

# Build TypeScript
npm run build

# Lint
npm run lint

# Bundle for distribution (local testing only — CI builds on release)
npm run bundle

# Run all checks
npm run all

Releasing

1. Create a GitHub Release with a semver tag (e.g., v1.0.0)
2. The release workflow automatically builds dist/, commits it, and updates the v1 major version tag
3. Users referencing @v1 get the latest release automatically

License

MIT