Skip to content

Release confidence with SDETKit (canonical explainer)

DevS69 SDETKit gives engineering teams deterministic release go/no-go decisions with machine-readable evidence, using one repeatable command path from local to CI.

What release confidence means in this repo

Release confidence means a repository can answer "Is this ready to ship?" with repeatable command outcomes plus structured artifacts, not only ad hoc terminal interpretation.

Canonical command path (primary)

python -m pip install "git+https://github.com/sherif69-sa/DevS69-sdetkit.git"
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

Canonical proof contract (local and CI)

Invariant path: - Local run uses the same gate path as CI evidence review: gate fast -> gate release -> doctor. - CI preserves the same JSON decision objects as artifacts.

Invariant artifacts:

build/
├── gate-fast.json
└── release-preflight.json

Invariant fields for first triage: - ok - failed_steps - profile

Go/no-go support model: - ok gives deterministic pass/fail. - failed_steps gives first remediation targets. - profile confirms which lane produced the result.

External-first-run trust model: - First run is considered trustworthy when commands always emit inspectable JSON artifacts, even when gates fail. - Missing artifacts are contract failures; failing gates with artifacts are expected triage behavior in many fresh repos.

Automated contract guard:

python -m pytest -q tests/test_external_first_run_contract.py

Primary vs optional

Primary (use first)

  • gate fast
  • gate release
  • doctor
  • JSON artifacts in build/ for review decisions
  • CI artifact decoder: CI artifact walkthrough

Optional (use later)

  • Team rollout documents and stricter CI layers
  • Broader command families (intelligence/integration/forensics)
  • Advanced references and integrations

Local and CI stay aligned

  • Local developer run: execute canonical commands directly.
  • CI run: execute same core commands and upload JSON outputs.
  • Review: use artifact fields as source-of-truth before log deep-dives.

Canonical CI rollout details: Recommended CI flow.

What this does not try to be

  • Not a replacement for every underlying lint/test/security tool.
  • Not an attempt to maximize command surface area for first-time users.
  • Not a claim that every repo needs full enterprise policy layers on day one.

SDETKit focuses first on deterministic release-confidence decisions and evidence clarity.