Newman alternative for CI

DevTools CLI executes YAML flows in parallel, with machine‑readable outputs and exit codes designed for pipelines.

Why teams move off Newman

Slow runs and heavy scripting
Mixed reporting; brittle CI plumbing
Hard to track variable mappings at scale

DevTools CLI

Parallel by default; multithreaded Go runner
JUnit/JSON reports, clean exit codes
Flows exported as human‑readable YAML

Install

curl -fsSL https://sh.dev.tools/install.sh | bash

See the CLI reference.

Example (GitHub Actions)

name: API tests on: [push] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Install DevTools CLI run: curl -fsSL https://sh.dev.tools/install.sh | bash - name: Run flows (JUnit) run: devtools flow run --report junit:test-results.xml tests.yaml

Deep dive guide

For a step‑by‑step walkthrough and CI tips, see the Newman alternative CI guide.

Running tests in CI is half the job; keeping them current is the other half. Stresseur, the AI test engineer for APIs, proposes test updates on every PR and runs from the CLI inside Claude Code and Cursor (early access).