Quality & Health

sate version-stability

Shipped (partial)

Per-test analyzer: captures a stability contract describing how a single test depends on Laravel-version-specific behaviour.

What it does

Reads ONE test file at a time (not a whole suite) and produces a JSON contract listing the Laravel-version-sensitive symbols the test depends on. Used downstream to predict which tests will need attention on a Laravel major-version upgrade.

Who runs this

→Teams planning a Laravel major-version upgrade
→Maintainers of high-value (golden) tests preparing for version drift

How to invoke

node analysis/version-stability/cli.js <test-file> [project-root] [output-file]

Flags

<test-file>

Required. Path to the single test file to analyse.

[project-root]default: cwd

For PSR-4 resolution.

[output-file]

Optional output path; otherwise JSON to stdout.

What it produces

·JSON contract (~few KB per test)

What it does NOT do

✖Does NOT analyse the whole suite at once — call per test file
✖Does NOT predict pass/fail across versions — only contract surface

Notes

In audit-all, the top 5 golden tests are sampled automatically.

Status

Engine tests

Status

Shipped (partial)

Related pipelines

sate golden

Identifies high-value tests — the ones that protect your business core (payments, billing, auth, subscriptions).

sate audit-all

The front door: runs every read-only pipeline against your project and writes both a developer report set and a non-technical owner summary.