Issue your
first receipt.

Run one critical journey, seal the result, and publish a release decision.

testkit / quickstartready

npm install --save-dev @(scope)/testkit

# 02 / run the project suites
npx testkit run

# 03 / issue the Cloud receipt
npx testkit cloud apply --file .testkit/results/latest.json

✓ receipt issuedtestkit.cloud/r/tk_8f31a2

02 / Delegate

Tell your agent
what to verify.

Give it one behaviour and a clear stopping point. The suite stays beside the product code it checks.

Prompt / coding agentcopy and edit

Inspect this repository.

Add one colocated Testkit suite for [behaviour].
Choose an engine supported by the suite type.
Run it and report the result and evidence path.

Do not change product code.

Expected owner

src/checkout/__testkit__/
checkout.ui.testkit.ts

Terminal / repository rootdiscovery

npx testkit discover --output-mode verbose

ServiceTypeEngineSuite

checkoutuiplaywrightcheckout.ui.testkit.ts

1 suite ready

03 / Inspect

Check what
Testkit found.

Discovery shows the owner, test type, engine, and suite before Testkit schedules any work.

04 / Work locally

Run the whole project
or one boundary.

Use the complete run for release confidence. Narrow the next run while you work, then read the latest recorded status.

Commands / local looprun and rerun

# Run every discovered suite
npx testkit run

# Narrow the next run
npx testkit --service checkout --type ui

# Read the latest result
npx testkit status

Output / .testkitrecorded locally

.testkit/results/
├── latest.json
└── runs/
    └── <run-id>/
        ├── service logs
        ├── runtime output
        └── emitted artifacts

Latest is a convenient view Each run remains under runs/

05 / Publish

What happens next

Verified at lightning speed.

Testkit checks the bundle in the cloud. GitHub gets the answer.

npx testkit cloud apply \
  --file .testkit/results/latest.json

01Schema and digest checked
02Receipt stored with evidence
03Release decision published

Implementation detailRead the full setup↗