Slides are shown one under the other. Presentation mode needs JavaScript. All presentations · Türkçe sürüm
Testnizer Training · hands-on · v1.6.0

Getting started

From install to your first MCP tool call — step by step.

Fourteen short steps. Each one says what you do, where you click and what you will see. After the first requests everything runs on your own machine — no account, no API key, no tokens spent.

≈ 60–90 minutes Testnizer 1.6.0 macOS 13+ · Windows · Linux
Press → to start

The plan

Fourteen steps, each one a few minutes.

Install and create a projectmacOS · Windows · Linux
Send your first requesthttpbin.org
Environments and {{variables}}one value, every request
AuthorizationBearer token, inherited
Scripts and testspm.test, assertions
Run a folder, export the reportRunner · HTML
An HTTP mock server127.0.0.1:3001
An MCP mock server, connectedEcho preset
Call an MCP toolecho · pm.mcp
Scan the MCP serverA–F report
AI Chat with MCP toolsno API key
Import from Postmanfile, folder or .zip
Work as a team with Gitcommit, push, pull
Shortcuts and tipsCmd/Ctrl + …

You need Testnizer 1.6.0 and an internet connection for steps 2–4 (they call httpbin.org). Everything from step 7 on talks to servers that Testnizer itself runs on 127.0.0.1.

01 / 14Install

Install Testnizer and create a project.

What you do

Download the build for your system from testnizer.com/download, install it and open it. Then create the project this training works in.

Where you click
  1. Home
  2. New Project
  3. Create New
  4. Petstore
  5. Create
What you will see

An empty project. The rail on the left: APIs, Tests, Mocks, History, Tools, Security and Settings at the bottom. No sign-up screen — there is no account.

Where your data lives
macOS~/Library/Application Support/Testnizer/
Windows%APPDATA%\Testnizer\
Linux~/.config/Testnizer/

02 / 14First request

Send your first request.

What you do

Open an HTTP tab, call a public echo service, read the answer — then save it with Ctrl/Cmd S into a new folder called httpbin.

Where you click
  1. + New
  2. HTTP
  3. GET
  4. https://httpbin.org/get
  5. Send
What you will see

Status, time and size above the response, the JSON body and the headers. The Console (Ctrl/Cmd Alt C) shows the raw request and response.

03 / 14Environments

Put the host and the token in an environment.

What you do

Create an environment with baseUrl = https://httpbin.org and token = sk-demo-1234 (type secret), make it active, and change the URL to {{baseUrl}}/get.

Where you click
  1. environment selector, right end of the tab bar
  2. Manage Environments
  3. New Environment
  4. Add Variable
  5. Set Active
What you will see

The same response as before — the variable is resolved when you send. The secret is masked in History and the Console, encrypted on disk where the OS has a keychain, and left out of Git commits and exports.

04 / 14Authorization

Send a bearer token — once, for the whole folder.

What you do

Set the token on the httpbin folder, then add a request to {{baseUrl}}/bearer in that folder whose auth is Inherit from parent.

Where you click
  1. right-click the folder
  2. Settings
  3. Authorization
  4. Bearer Token
  5. {{token}}
What you will see

200 with "authenticated": true. Remove the token and the same call answers 401. The nearest setting wins: request, then folder, then project.

05 / 14Scripts and tests

Make the request check its own answer.

What you do

On the /bearer request, write two pm.test checks — or add them without code as assertions. Postman scripts run as they are.

Where you click
  1. Scripts
  2. Post-response
  3. or
  4. Tests
  5. + Add Assertion
What you will see

After Send, the response's Test Results tab lists each check as passed or failed. The same script behaves the same in the Runner.

06 / 14Runner

Run the whole folder and keep the report.

What you do

Save both requests (Ctrl/Cmd S), then run the httpbin folder in one go and export the result as a single HTML file.

Where you click
  1. right-click the folder
  2. Run
  3. Start run
  4. Export HTML
What you will see

One row per request with its status, time and tests, a passed / failed total, and a report you can open in any browser — credentials masked. Iterations, data files, Setup and Teardown are on the same screen.

07 / 14Mock server

Start a mock API on your own machine.

What you do

Create an HTTP mock from the ready-made REST example — a small Users API — start it and call it from a request tab.

Where you click
  1. Mocks
  2. New mock server
  3. HTTP
  4. REST example
  5. Create
  6. Start & open in request tab
What you will see

The server on http://127.0.0.1:3001. GET /users/2 answers a user, /users/7 answers 404. Every call appears in the mock's Logs tab. A saved folder can become a mock too: right-click → Create Mock Server from this folder.

08 / 14MCP

Start an MCP server and connect to it.

What you do

Create an MCP mock from the Echo preset — one echo tool that returns its text — and open it in an MCP tab, already filled in.

Where you click
  1. Mocks
  2. New mock server
  3. MCP
  4. Echo
  5. Start & open in MCP tab
  6. Connect
What you will see

Streamable HTTP to http://127.0.0.1:3100/mcp, the negotiated protocol version, the server's name, and the Tools tab with echo. Under Messages, Frames shows the handshake as raw JSON-RPC.

09 / 14Tool call

Call the tool, then save the call with a test.

What you do

Fill the text argument from the form Testnizer builds out of the tool's schema, run it, and save the call so it can run again in the Runner.

Where you click
  1. Tools
  2. echo
  3. text: hello
  4. Run
  5. Ctrl/Cmd S
What you will see

The result with hello in its content, the time it took, and a tools/call pair in Frames. A post-response test can read it through pm.mcp.

10 / 14Security scan

Scan the server and read the report.

What you do

Run the security scan against the Echo server you are connected to. It is your own server on your own machine, so you are allowed to test it.

Where you click
  1. Security
  2. Scan
  3. open a finding
  4. Save HTML report…
What you will see

A grade from A to F, a score out of 100 and the checks by category — each with its evidence. Plain HTTP on 127.0.0.1 is only noted. Rate-limit checks need Include active probes, which is off by default. Your grade depends on the server's settings.

11 / 14AI Chat

Let a model call your tool — and approve it.

What you do

Start an AI mock with the Tool call round-trip preset — it plays a model that asks for a tool. Give the chat the Echo call you saved in step 9 and send a prompt. No provider key is used.

Where you click
  1. New mock server
  2. AI
  3. Tool call round-trip
  4. Start & open in AI Chat tab
  5. Add a saved MCP request…
  6. Load tools
  7. Allow once
What you will see

An approval card with the tool and its arguments before anything runs — approval is on by default, “Run tools without asking” lasts for this tab only. Then the tool result, the reply and its time and token counts.

12 / 14Import

Bring a Postman collection in, scripts and all.

What you do

Import a collection exported from Postman — a v1, v2.0, v2.1 or v3 file, a v3 Native Git folder, an environment or a .zip. The version is read from the file.

Where you click
  1. Ctrl/Cmd O
  2. Postman
  3. choose the file
  4. or
  5. Import folder…
What you will see

A report of what came in, what was skipped and what could not be carried — for example Kafka and Postman Data requests in a v3 collection are skipped. Collection auth lands on the folder; requests inherit it.

13 / 14GIT

Share the project through your Git repository.

What you do

Connect the project to a repository and push it. A teammate picks it up with Clone from Git on the New Project screen and pulls your later changes.

Where you click
  1. Settings
  2. Storage
  3. Save Mode: Git
  4. branch menu
  5. Commit…
  6. Commit and push
What you will see

The changed requests, environments and suites to commit. Your token goes out empty — after a pull your teammate sees how many secrets to fill in. Scripts in the cloned project wait until they allow them.

14 / 14Shortcuts and tips

Ten keys that save you the most clicks.

Ctrl/CmdEnterRun the active request
Ctrl/CmdSSave the request
Ctrl/CmdKCommand palette
?Every shortcut, on one sheet
Ctrl/CmdNNew request tab
Ctrl/CmdLFocus the URL bar
Ctrl/CmdBShow or hide the sidebar
Ctrl/CmdAltCShow or hide the Console
Ctrl/CmdOImport
Ctrl/Cmd,Settings

Paste a cURL into the URL bar

It becomes a full request — method, headers, body, auth. One Undo puts the text back.

Generate Code — 36 variants

Turn the open request into code for your language. Secret variables stay as {{name}} unless you choose to include them.

118 dynamic variables

{{$randomEmail}}, {{$guid}}, {{$timestamp}} … — the same names as Postman.

Testnizer

That's the tour. Now try it on your own API.