Testnizer

Features

A complete reference of everything Testnizer does — protocols, auth, variables, testing, runner, mocking, import/export, code generation, and the built-in tools.

The full capability surface of Testnizer, grouped by area. Everything below runs 100% locally — no account, no cloud, no telemetry. For deeper pages, follow the links in each section.

Protocols

Every protocol is a first-class request type with its own editor, response panel, and Node-side engine — not a plugin. See Protocols overview.

ProtocolHighlights
HTTP / RESTMethods, body modes, redirects, timeout, mTLS, scripts, assertions
SOAP / WSDLWSDL import, manual envelope, operation picker
WS-SecurityUsernameToken, Timestamp, RSA-SHA256 signing, encryption — see WS-Security
GraphQLQuery, mutation, subscription, schema introspection
gRPCProto load + server reflection, all four streaming modes
WebSocketwss, params + custom headers, Text / JSON / XML / HTML / binary composer, saved messages, hexdump, bidirectional timeline
Socket.IOClient v4 / v3 / v2, namespaces, listeners, Ack, multi-argument emit, saved messages, event timeline
MQTT3.1.1 and 5.0, mqtt(s):// and ws(s)://, topics, QoS, retain, Last Will, saved messages
SSELong-lived streams, named events, Last-Event-ID resume — see SSE
MCPStreamable HTTP / SSE / stdio; tools, resources, prompts, notifications, OAuth 2.1, security scan
AI ChatMultiple LLM providers + custom URL, streaming, MCP servers as tools with per-call approval, local conversations — see AI Chat

Building requests

  • Method + URL bar with live query-param ↔ URL sync
  • Headers with bulk edit
  • Body modes: raw / JSON / XML / HTML / text, form-data (file upload), x-www-form-urlencoded, binary
  • Paste a cURL command into the URL bar to turn it into the request
  • Path variables (:id in the URL path) in their own table
  • The Headers tab lists the automatic headers (Accept, User-Agent, Host, Content-Type, Content-Length, auth, cookies) and where each comes from; a header you add overrides the automatic one
  • Per-request timeout, redirect following (max redirects), SSL verification toggle — saved with the request and inherited from Project Settings, then App Settings, when you leave them untouched
  • Pre-request and post-response script tabs

Authentication

Basic · Bearer Token · API Key (header or query) · OAuth2 · Digest · NTLM · Hawk · AWS Signature.

Variables & environments

See Environments & variables.

  • Environments scoped per project, with a dual Initial / Current Value model
  • Globals per project — Postman globals and collection variables in one list, with Move to Globals for an environment
  • {{variable}} substitution with chained references
  • Dynamic values: {{$randomInt}}, {{$guid}}, {{$timestamp}} and more
  • Inline variable autocomplete

Testing & assertions

Code-free assertions: status equals, status in range, body contains, header exists / equals / contains, response time under, response size under. Assertion values themselves resolve {{variables}}. See Scripts & test assertions.

Scripting

Postman / Insomnia-compatible pm.* API, the same one on Send and in the Runner:

  • pm.environment / pm.globals / pm.variables / pm.collectionVariables get & set, and pm.vault for secret Globals
  • pm.test(), pm.expect() (chai-BDD chain), pm.response
  • pm.iterationData, pm.execution.skipRequest() / setNextRequest()
  • All 118 Postman dynamic variables ({{$randomEmail}} …)
  • Scripts are not sandboxed, so a project that arrives from Git or a project file runs none until you allow it on this computer

Running collections

See Collection runner & automation.

  • Sequential multi-request runs, iterations + data-driven rows (CSV / JSON)
  • Delay between requests, stop-on-error, environment selection; the results name the environment the run used
  • Critical request — a request that stops the run when it fails, whatever stop-on-error says
  • A Run fail script that fires only when the run is red
  • HTML & JSON reports from one report builder, run history + statistics
  • Scheduler for recurring runs
  • MCP requests run too, with the same pass / fail rules as Send
  • Right-click Run on any folder or collection
  • Test Suites — sets built from multiple collections, each item a full request snapshot

Mock server

Real servers on 127.0.0.1, in four kinds, all in the Mocks panel. See Mock servers.

  • HTTP — rule-based endpoints with {{variable}} templating, conditional rules, scripted responses, auth, rate limiting, failure injection and schema validation; create one from an OpenAPI / Swagger / Postman file or from a folder of saved requests
  • SSE — streams events you define, with interval, heartbeat, loop and Last-Event-ID resume
  • AI (LLM) — answers the OpenAI chat and Anthropic messages APIs, with streaming and deliberate mid-stream errors
  • MCP — a local MCP server with tools, resources, prompts, bearer auth and error scenarios

Import & export

See Import & export.

  • Import: OpenAPI / Swagger, Postman (v1 – v3, folders, .zip), Insomnia, HAR, cURL (bash, CMD, PowerShell — or paste into the URL bar), WSDL, RAML, SoapUI, Testnizer Native — with auto format detection
  • Export: full project or folder subtree — Testnizer JSON, Postman v2.1 / v3, OpenAPI 3, Insomnia

Code generation

Generate a ready-to-paste request snippet in 20 languages and 36 variants — cURL (bash, CMD, PowerShell), JavaScript (Fetch / XHR / jQuery), NodeJS, Python, Java, C#, Go, PHP, Ruby, Kotlin, Swift, Rust, Dart, R, C, Objective-C, OCaml, PowerShell, Shell (wget / HTTPie) and raw HTTP — with per-variant options. See Code snippet generation.

Built-in tools

Offline, browser-safe utilities — see Built-in tools and the JWT Debugger:

JWT · JSONPath · XPath · XSLT · Hash · HMAC · Encoders (Base64 / URL) · Base converter · Regex tester · Diff · Epoch / timestamp · UUID generator · JSON ↔ XML · YAML ↔ JSON · Jolt transform · JSON Schema · JSON / XML formatter · HTTP status reference · WS-Security helper.

Security tools

The Security page collects the key, PKI, token and identity suite: Keystore Studio (JKS / PKCS#12), JWK / JWKS, the JWT / JOSE debugger (sign, verify, JWE), the TLS Inspector, SAML build / sign / validate, plus an OTP Authenticator (TOTP / HOTP), a Password Generator and a QR tool. All of it runs offline — except the TLS Inspector, which by design connects to the endpoint you point it at.

Organization & version control

  • Workspaces → Projects → Branches hierarchy
  • Git integration (per-project branches, a Commit panel with selective commit, Pull / Push / Merge, conflict handling) — see Git integration
  • Endpoint / folder tree with drag-and-drop ordering
  • Tree search that keeps a matching folder’s whole subtree — root-level requests included (Postman / Insomnia behaviour)
  • Right-click a folder → Expand All / Collapse All for the whole subtree, even while a search filter is active

Request history

Local request history with full request/response snapshots, “Today” grouping, and a detail panel. Credentials and your secret values are masked before a row is stored. See Request history.

Response viewing

  • Status / timing / size metadata, Monaco JSON syntax highlighting
  • Response · Cookies · Headers · Console · Actual Request tabs
  • Timing breakdown (DNS / TCP / TLS / TTFB / download)

Certificates & TLS

mTLS / client certificates, TLS presets, Legacy TLS routing for old servers, custom truststore, and encrypted passphrase storage. See Certificates.

Security & privacy

  • Optional app password (a lock on launch, not database encryption)
  • Secret variables, mock tokens and certificate passphrases are encrypted with the operating system’s keychain in the local database, and are written empty to every file that leaves the app (Git, exports)
  • History, the Console, run reports and mock logs mask credentials
  • EULA / privacy consent on first run
  • contextIsolation on, nodeIntegration off, a sandboxed renderer, web permissions denied by default, strict CSP — the UI never touches the network directly; all traffic goes through the Node main process

See Why offline?.

Platform

  • Windows, macOS 13 (Ventura) or later, Linux (x64 + arm64)
  • Standalone & 100% offline — zero external dependencies
  • Local SQLite storage, with a database backup taken before each update — see Getting started
  • Auto-update built in
  • Native open / save / message dialogs