Skip to content

Start here: deterministic release confidence

Live-adoption product proof

The current package is backed by a committed live-adoption proof pack:

  • Proof page: Live-adoption product proof
  • Decision: SHIP with known STRICT_FINDINGS
  • Blocking failures: 0
  • Known strict finding: legacy-noargs compatibility behavior only
  • Validated strengths: first-proof, core gates, review JSON/operator JSON, wheel smoke, fixture surfaces, and docs front-door commands.

DevS69 SDETKit is a release-confidence CLI for deterministic ship/no-ship decisions with machine-readable evidence.

From noisy CI evidence to a reviewable decision, diagnosis, and exact next command.

Primary outcome: know if a change is ready to ship.

Canonical first path: python -m sdetkit gate fast -> python -m sdetkit gate release -> python -m sdetkit doctor.

This page is the product homepage/router for first-time adoption.

⚡ Fast start · 🧭 Repo tour · 🛠 CLI commands · 🩺 Doctor checks · 🤝 Contribute · 📦 Legacy reports

Top journeys

  • Run first command in under 60 seconds
  • Validate docs links and anchors before publishing
  • Ship a first contribution with deterministic quality gates

Why teams use SDETKit

  • Release owners: deterministic SHIP / NO-SHIP evidence.
  • SDET and QA engineers: the first meaningful failure rather than a wrapper verdict.
  • Platform teams: machine-readable evidence and exact proof commands.
  • Reviewers: explicit review-first authority boundaries.

Failure to next action

classification: test
first_failure: FAILED tests/test_release_contract.py::test_wheel_smoke
affected_file: tests/test_release_contract.py
verification: python -m pytest -q tests/test_release_contract.py -o addopts=
decision: review-first

Use First failure triage for the shortest operator path and Investigation operator guide for the full safety contract.

Public launch proof

The public launch proof shows a realistic saved pytest failure reduced to its first failing node, owning file, focused proof command, and review-first decision. It also profiles a fixture-based Python, JavaScript/TypeScript, and Go repository without dependency installation, target-code execution, target mutation, or merge authorization.

The artifacts are reproducible, tied to an immutable source SHA, accessible as text, and marked main-only until the qualified 1.1.0 release.

Fast start

python -m sdetkit gate fast --format json --stable-json --out build/gate-fast.json
python -m sdetkit gate release --format json --out build/release-preflight.json
python -m sdetkit doctor

Generated artifacts:

build/gate-fast.json
build/release-preflight.json

New teams should stop here first, inspect the evidence, and only then expand into advanced lanes.

Choose your path

Operator path

Safety boundary: adoption and learning outputs are advisory unless an explicit guarded policy says otherwise.

Adoption and team rollout

SDETKit can inspect cloned external repositories in read-only mode, keep artifacts outside the target repository, and report unknown surfaces as review-first.

Quality, security, and remediation

Contributor and developer path

Architecture and evidence

Legacy reports

Historical and transition-era references remain intentionally secondary to first-time adoption. Use the archive index only after the canonical first proof path is operating.

Install and runtime notes

  • Python 3.10+
  • Prefer isolated environments.
  • Validate docs with NO_MKDOCS_2_WARNING=1 python -m mkdocs build -q.