agentiqa/Agentiqa — End-to-End Agentic QA in CI

E2E tests written in plain English, run against your live app. Results, videos and run links right in your workflow.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
service-keyProject-scoped Agentiqa CLI service key (sk_...). Required. Mint one from the Agentiqa web app or desktop app (Project Settings -> CLI Service Keys -> Create Key) or via /api/cli-quickstart-key. Pass it from a repository secret; never inline.yes
api-urlOverride the Agentiqa control-plane API URL (AGENTIQA_API_URL). Leave empty to use production (https://agentiqa.com). Set to https://s.agentiqa.com to target staging.no""
runtimeAdvanced. Where the execution engine runs; defaults to `cloud` — the browser runs on Agentiqa's infrastructure with the managed LLM and no Chromium on the runner. Leave unset for the standard hosted flow.nocloud
engine-urlOptional hosted-engine URL override; only meaningful with `runtime: cloud`. Leave empty for the default Agentiqa cloud engine (https://engine.agentiqa.com). Set https://s-engine.agentiqa.com for staging, or the URL of your own hosted engine.no""
gemini-api-keyAdvanced. Ignored for cloud runs, which use Agentiqa's managed LLM. When set, pass it from a repository secret.no""
plan-idRun a single test plan by id (tplan_...). Overrides label-ids when set.no""
label-idsComma-separated label ids; runs all plans tagged with any of them. Ignored when plan-id is set.no""
modeExecution order for the selected plans: sequential | parallel.nosequential
cli-versionVersion of the Agentiqa CLI to run: an npm dist-tag (latest, staging) or an exact semver (e.g. 1.4.2). Default latest.nolatest
artifacts-dirDirectory (relative to the workspace) for run artifacts and the JSON result envelope.noagentiqa-artifacts
fail-onExit-code gating policy. One of: never - never fail the job on the run outcome (report-only; read outputs downstream). plan-failure - (default) fail when a plan failed (exit 1) OR on a config/usage error (exit 2 — permanent, must fail loudly). Only retryable infra errors (exit 3) are swallowed, surfacing as outcome=infra-error for a digest/reporter to handle. Exit 3 also covers a NO-VERDICT batch — one whose only non-passing plans could not reach a verdict (a persistent engine disconnect, or the blocked cascade of one) — so a transient WS drop no longer reads as a red plan-failure. Read the `outcome` step output to gate more strictly (fail-on: any). any - fail on any nonzero exit. Use for release gates.noplan-failure
node-versionNode.js version to set up on the runner (18+).no22
upload-artifactsUpload the artifacts directory (screenshots/video/result JSON) as a build artifact.notrue
artifact-nameName for the uploaded artifact. Defaults to agentiqa-artifacts-<run_id>-<attempt> when empty.no""
share-linksMint an opt-in PUBLIC, revocable share link for each cloud run (passes --share to the CLI) so reviewers can open a run from the step summary without an Agentiqa login. The Run column links the share URL when present. Default false (privacy-conservative). Cloud runtime only.nofalse
retention-daysRetention period (in days) for the uploaded artifact. Only applies when upload-artifacts is true. Defaults to 14; the repo/org artifact-retention cap still bounds it.no14
namedescription
outcomeRun outcome bucket: passed | plan-failure | config-error | infra-error. Note: exit 0 with zero executed plans buckets as config-error (a run that tests nothing is not a pass).
json-pathPath to the captured JSON result envelope (schemaVersion:1). Empty if the run was not attempted.
exit-codeRaw CLI process exit code (0 pass / 1 plan failure / 2 usage-config / 3 infra).
plans-totalTotal plans reported in the JSON envelope (empty if no envelope).
plans-passedNumber of plans with outcome=passed.
plans-failedNumber of plans with outcome != passed.
artifact-nameResolved artifact name used for the upload.
cli-resolved-versionThe Agentiqa CLI version actually executed, resolved at run time from `agentiqa --version` (e.g. 1.1.32). Makes verdict drift across publishes attributable when cli-version is a floating dist-tag (latest/staging). Empty if capture failed or the run was not attempted.