Offline, read-only validation of a locally maintained quarantine register and complete test-outcome export. It produces an exact-match CI policy preview; it does not modify CI, fetch failures, or write files.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/flaky-test-quarantine-register.mjs --root examples/pass --input register.json
node bin/flaky-test-quarantine-register.mjs --root examples/fail --input register.json
npm run checkRead the result
--help prints usage. Normal runs emit one JSON report on stdout: exit 0=pass, 1=fail, 2=incomplete or invalid configuration. Invalid options or root produce empty stdout; an unreadable, undecodable, malformed, or out-of-root named input produces an incomplete report. The named input is realpath-confined under the root. UTF-8 decoding is strict and duplicate decoded JSON keys are rejected. No files are written.
Where this check stops
Input ≤65,536 bytes, ≤100 quarantines, ≤200 outcomes, opaque IDs ≤128 UTF-16 units, pass streak and recovery requirement 1–100 (failed streak exactly 0), JSON depth ≤16, and evaluation time ≤5,000 ms through an injected monotonic clock. Each inclusive maximum accepts N and rejects N+1. Dates are strict YYYY-MM-DD calendar dates. No automatic quarantine creation, CI writes, live test runs, legal retention opinion, or inference of flaky behavior is performed.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.