AgentKit
DocsKitsCLI ReferenceDesktop App

test

ak test classify-e2e

Advise on changed E2E scenario classes without changing scheduling

Use ak test classify-e2e for the operation described below. The command help records its arguments, effects, and options.

Semantic modes use the e2e-classification consumer. A provider call happens only when you have enabled semantic_decision at user scope, set semantic_decision.consumers.e2e-classification to true, and supplied TYPESAFE_API_KEY in the environment. The grant is required even when you have no consumers map. See ak config prefs set.

Command contract

Advise on changed E2E scenario classes without changing scheduling

Synopsis

Compare top-level E2E tests against a Git base, including dirty and untracked files. Optional provider advice requires explicit e2e-classification consent and a key. Unknown effects cannot establish parallel hermetic isolation. The class manifest remains authoritative.

Effects: Reads local Git and Go source. When explicitly configured, sends only bounded structural facts to the provider. Optionally creates a receipt; never changes classifications or scheduling.

Exit status: 0 discovery and advisory status reported 1 invalid input, stale advice, or output failure 2 invalid arguments

ak test classify-e2e [flags]

Examples

  ak test classify-e2e --base origin/dev --json
  ak test classify-e2e --base origin/dev --facts reviewed.json --output advice.json

Options

      --base string      Git base compared with the current checkout (required)
      --facts string     Optional repository-local reviewed structural facts JSON
  -h, --help             help for classify-e2e
      --json             Emit machine-readable JSON (implies --no-interactive)
      --no-interactive   Disable interactive prompts (CI-safe)
      --output string    Create a new JSON advice receipt; never overwrite
  -q, --quiet            Suppress non-error output on stderr
  -V, --verbose          Extra diagnostic output on stderr (loses to --quiet)
  -y, --yes              Assume yes for all prompts

SEE ALSO

  • ak test - Plan and execute repository test-impact checks