Recommended path

Run your first adaptive selection.

Create a workspace, install the CLI, initialize your repository, sync the test library, request a subset, and inspect the decision in the dashboard.

Create Free Workspace Install CLI

First adaptive selection

Create a free workspace

Create a project

Name the system Quantik Mind™ will analyze.

Generate an API key

Create the credential used by the CLI and CI/CD.

Install Quantik Mind™ CLI

Use the Python package or a platform binary.

Initialize the local project

Create qmind.yaml and connect local credentials.

Installation

Package and binary options.

Install the Python package or download a platform binary from the latest GitHub Release.

Python Package

Install the CLI in Python environments, virtualenvs, and CI runners.

pip install quantikmind-cli

Windows Binary

Use the packaged executable on Windows workstations and runners.

Download from latest release

macOS Binary

Install locally on macOS for repository setup and scripted workflows.

Download from latest release

Linux Binary

Use the Linux binary on developer machines, agents, and build runners.

Download from latest release

CLI

Use real qmind commands.

Quantik Mind™ decides which tests should run. Your existing test framework still executes them.

Framework options include Playwright, Cypress, Selenium through your runner, Pytest, Jest, Maven, Gradle, RSpec, Cucumber, Robot, and other supported CLI integration targets.

Initialize the local project

Creates qmind.yaml, connects local credentials, and records the framework and test result locations.

qmind init --api-key $QM_API_KEY --project-name "my-project" --framework playwright --test-dir tests --results-dir test-results --non-interactive

Verify configuration

Shows Quantik Mind™ configuration status for the local repository.

qmind status

Sync the test library

Generates and uploads a functional test library from local tests.

qmind sync library

Request a selected subset

Requests the selected test subset for the current change context.

qmind subset --framework playwright --changed-file src/checkout.ts

Inspect JSON output

Returns machine-readable selection output for scripts and CI adapters.

qmind subset --framework playwright --changed-files-file changed-files.json --json

Record execution metadata

Records build and test execution metadata after the runner has executed tests.

qmind record build
qmind record tests

CI/CD integration

Select before the runner executes.

These pipelines initialize Quantik Mind™, synchronize the test library, record the build, and produce the selected scope. Your repository-specific adapter passes that scope to the test runner.

GitHub Actions

.github/workflows/adaptive-tests.yml

Use repository secrets for the Quantik Mind™ credentials, then generate the selected scope before your runner step.

name: adaptive-tests

on:
  pull_request:
  push:

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

      - name: Install Quantik Mind CLI
        run: pip install quantikmind-cli

      - name: Initialize Quantik Mind
        run: |
          qmind init \
            --api-key "${{ secrets.QMIND_API_KEY }}" \
            --api-url "${{ secrets.QMIND_API_URL }}" \
            --project-id "${{ secrets.QMIND_PROJECT_ID }}" \
            --framework playwright \
            --test-dir tests \
            --results-dir test-results \
            --non-interactive

      - name: Sync test library
        run: qmind sync library

      - name: Record build metadata
        run: qmind record build

      - name: Request selected subset
        run: qmind subset --framework playwright --changed-files-file changed-files.json --json > selected-tests.json

GitLab CI

.gitlab-ci.yml

Store QMIND_API_KEY, QMIND_API_URL, and QMIND_PROJECT_ID as protected CI/CD variables.

stages:
  - test-selection

adaptive-tests:
  stage: test-selection
  image: python:3.12
  script:
    - pip install quantikmind-cli
    - qmind init --api-key "$QMIND_API_KEY" --api-url "$QMIND_API_URL" --project-id "$QMIND_PROJECT_ID" --framework playwright --test-dir tests --results-dir test-results --non-interactive
    - qmind sync library
    - qmind record build
    - qmind subset --framework playwright --changed-files-file changed-files.json --json > selected-tests.json
  artifacts:
    paths:
      - selected-tests.json

Azure DevOps

azure-pipelines.yml

Provide the three Quantik Mind™ values as secret pipeline variables or through a secured variable group.

trigger:
  - main

pool:
  vmImage: ubuntu-latest

steps:
  - checkout: self

  - script: pip install quantikmind-cli
    displayName: Install Quantik Mind CLI

  - script: |
      qmind init \
        --api-key "$(QMIND_API_KEY)" \
        --api-url "$(QMIND_API_URL)" \
        --project-id "$(QMIND_PROJECT_ID)" \
        --framework playwright \
        --test-dir tests \
        --results-dir test-results \
        --non-interactive
      qmind sync library
      qmind record build
      qmind subset --framework playwright --changed-files-file changed-files.json --json > selected-tests.json
    displayName: Select adaptive test scope

Jenkins

Jenkinsfile

Bind the Quantik Mind™ values from Jenkins Credentials and request the subset inside a dedicated stage.

pipeline {
  agent any

  environment {
    QMIND_API_KEY = credentials('qmind-api-key')
    QMIND_API_URL = credentials('qmind-api-url')
    QMIND_PROJECT_ID = credentials('qmind-project-id')
  }

  stages {
    stage('Adaptive test selection') {
      steps {
        sh 'pip install quantikmind-cli'
        sh '''
          qmind init \
            --api-key "$QMIND_API_KEY" \
            --api-url "$QMIND_API_URL" \
            --project-id "$QMIND_PROJECT_ID" \
            --framework playwright \
            --test-dir tests \
            --results-dir test-results \
            --non-interactive
          qmind sync library
          qmind record build
          qmind subset --framework playwright --changed-files-file changed-files.json --json > selected-tests.json
        '''
      }
    }
  }
}

REST API

Use the API for custom platforms and automation after the first CLI workflow is understood.

Open API documentation →

Observability

Observability is one source of Runtime Signals. Configure and verify it with real command groups.

qmind observability configure
qmind observability status

Local agent

Use qmind agent for local or runner-side agent workflows where needed.

qmind agent init
qmind agent start
qmind agent status
qmind agent stop

Benchmark reproduction

Reproduce the Google Online Boutique Benchmark from the Quantik Mind™ benchmark repository.

Open benchmark repository →

Examples

Common command patterns.

qmind subset --framework playwright --changed-file src/checkout.ts

qmind subset --framework pytest --changed-files-file changed-files.json --json

qmind observability configure

qmind observability status

qmind agent init

qmind agent start

qmind agent status

qmind agent stop

Dashboard

Inspect the decision.

The dashboard shows selected tests, skipped tests, risk coverage, decision rationale, and signal contribution.

Open Quantik Mind™ App

Selected

644 / 2175

Risk Coverage

68.8%

High-Risk

100%

Reduction

70.4%

Why Selected

SUPERPOSITION · execution value →

DEPENDENCY · runtime-critical path →

SIGNAL · changed checkout flow →