Step 1: Write .testneo files
Define clear, natural-language verification that teams can review and maintain.
Run natural-language verification from your shell and CI pipelines. Same Release Intelligence Layer, same release signals, same evidence model.
Use the CLI for automated verification in terminal workflows and CI gates.
Define clear, natural-language verification that teams can review and maintain.
Execute tests with project/environment context and collect results consistently.
Use outcomes for PASS/WARN/BLOCK release decisions with traceable logs.
$ npm install -g @testneo/cli
$ testneo config set apiKey tn_your_key
$ testneo config set projectId 47
$ testneo config set defaultEnvironment dev
$ testneo doctor
# ✓ API reachable · projects listed
$ testneo run login.testneo --wait --fail-on-error
Use TestNeo CLI to keep verification consistent from local terminal to production CI.