Converts a Postman collection to a k6 script.

The postman-to-k6 converter utilizes your Postman collection and converts all the Postman requests, including tests, variables, ... to K6 scripts that can be executed by K6 to run performance tests.

This project is a friendly fork of the original grafana/postman-to-k6 converter, actively maintained and open for new contributions.

• Features
• Installation
  • Local Installation (recommended)
  • Global Installation
• Usage
• Video introduction
• Options
  • Iterations
  • Environment Variables
  • Global Variables
  • CSV Data File
  • JSON Data File
  • K6 Param Options File
  • K6 Handle Summary as JSON
  • K6 Request tag
  • Separate
  • Skip Pre
  • Skip Post
  • CLI options file
• Examples
• Unsupported Features
• Other similar tools
• Credits

• Pre-request scripts.
• Test scripts.
• Variables (at all scopes + dynamic).
• Data files.
• Authentication methods (except Hawk).
• File uploads (experimental).
• postman.* interface (exceptions below).
• pm.* interface (exceptions below).
• Support for Postman Dynamic Variables & ReplaceIn function.
• Global variables exposed by Postman: globals environment data iteration.
• xml2Json conversion.
• All Postman Schema versions.

While possible to install globally, we recommend that you, if possible, add the converter to the node_modules of your test project using:

$ npm install -D @apideck/postman-to-k6

or using yarn...

$ yarn add @apideck/postman-to-k6

Note that this will require you to run the converter with npx @apideck/postman-to-k6 your-postman-file or, if you are using an older versions of npm, ./node_modules/.bin/postman-to-k6 your-postman-file.

$ npm install -g @apideck/postman-to-k6

To convert an exported collection to a k6 script:

$ postman-to-k6 collection.json -o k6-script.js

Then run the script in k6, as usual, using:

$ k6 run k6-script.js

Together with Nicole van der Hoeven & Paul Balogh from the K6 team, we talked about "postman-to-k6" in the K6 Office Hours podcast. We talked about how to convert a Postman collection to a k6 load test, the advantages of Postman, and the benefits of reusing automation testing scripts for performance.

Watch it on Youtube >> https://www.youtube.com/watch?v=Be66Db4wHLA

Topics covered:

• Use cases for k6
• Quick tour of Postman
• Why Postman is not designed for load testing
• Demo of postman-to-k6
• How to use Portman to generate tests from an OpenAPI spec

Configures how many times the script will be executed before completion.

Example:

$ postman-to-k6 collection.json --iterations 25 -o k6-script.js

Provide environment variables from a JSON file.

Example:

$ postman-to-k6 collection.json --environment environment.json -o k6-script.js

Provide global variables from a JSON file.

$ postman-to-k6 collection.json --global globals.json -o k6-script.js

Provide a data file in the CSV format.

$ postman-to-k6 collection.json --csv data.csv -o k6-script.js

Pass in a data file in the JSON format.

$ postman-to-k6 collection.json --json data.json -o k6-script.js

Pass K6 parameter options as a file in JSON format.

$ postman-to-k6 collection.json --k6-params k6-params.json -o k6-script.js

Output the K6 summary as a file in JSON format. This will add the K6 handleSummary(data) to the generated script, providing the functionality that K6 will store the summary output as JSON file locally.

$ postman-to-k6 collection.json --k6-handle-summary-json summary-report.json -o k6-script.js

Generate K6 request name tags based on available naming strategies:

• none: no automatic generated tags | default
• request: uses the request name as tag (example "Show all accounts")
• folder-request: uses Postman folder name and the request name (example: "Accounts - Show all accounts")

Example for request strategy

$ postman-to-k6 collection.json --k6-request-tagging=request -o k6-script.js

Example for folder-request strategy

$ postman-to-k6 collection.json --k6-request-tagging=folder-request -o k6-script.js

Split requests into separate files, for easier rearrangement of the logic.

$ postman-to-k6 collection.json --separate -o k6-script.js

$ postman-to-k6 collection.json -s -o k6-script.js

Skips any pre-request scripts during conversion

$ postman-to-k6 collection.json --skip-pre -o k6-script.js

Skips any post-request scripts during conversion

$ postman-to-k6 collection.json --skip-pre -o k6-script.js

Manage all the CLI options in a separate configuration file and pass them along to the postman-to-k6 command. To make the CLI usage easier, especially in CI/CD implementations.

All the available CLI options can be used in the config file. By passing the CLI options as parameters, you can overwrite the defined CLI options defined in the file.

$ postman-to-k6 collection.json --cli-options-file cli-config.json

Example of JSON CLI config file

{
    "output": "k6-script.js",
    "k6-params": "config/k6-params.json",
    "environment": "config/envs/team.env.json",
    "separate": true
}

A collection of Postman examples are located under example. To run one of the examples, just run it as you would any other command:

$ postman-to-k6 example/v2/echo.json -o k6-script.js

• Sending requests from scripts using pm.sendRequest.
• Controlling request execution order using postman.setNextRequest.
• Cookie properties, like hostOnly, session, and storeId.
• Textual response messages:
  • responseCode.name
  • responseCode.detail
  • pm.response.reason
  • pm.response.to.have.status(reason)
  • pm.response.to.not.have.status(reason)
• Properties returning Postman classes:
  • pm.request.url pm.request.headers
  • pm.response.headers
• The Hawk authentication method.
• Deprecated xmlToJson method.
• Request IDs are changed. Postman doesn't provide them in the export, so we have to generate new ones.

• jmeter-to-k6: Convert JMeter JMX files to k6 JS.

Special thanks to the K6 team from Grafana for open-sourcing & growing the converter and contributing it to the community. Thanks to bookmoons for creating this tool. Also, thanks to borjacampina for creating the original incarnation of the tool.