Question 1

How do I convert a Postman collection with environment variables to k6?

Accepted Answer

Use the --environment flag with a JSON file containing your variables. For example, run `postman-to-k6 collection.json --environment env.json -o script.js`, as described in the Environment Variables option.

Question 2

Does postman-to-k6 support file uploads in the converted scripts?

Accepted Answer

Yes, file uploads are supported, as listed in the Features section. The tool handles this conversion, allowing you to test API endpoints that require file data in k6.

Question 3

Postman-to-k6 vs jmeter-to-k6: which one should I use?

Accepted Answer

Choose postman-to-k6 if you have Postman collections, and jmeter-to-k6 for JMeter JMX files. Both are conversion tools, but they target different source formats, so pick based on your existing test suite.

Question 4

What happens if my Postman collection uses unsupported features?

Accepted Answer

Unsupported features like pm.sendRequest are ignored or may cause issues; check the 'Unsupported Features' section in the README. You might need to manually adjust the converted k6 script for full functionality.

Question 5

How can I skip pre-request scripts during conversion?

Accepted Answer

Use the --skip-pre flag when running the tool, as shown in the Options. For instance, `postman-to-k6 collection.json --skip-pre -o script.js` will exclude pre-request scripts from the output.

Question 6

Can I run postman-to-k6 in a Docker container?

Accepted Answer

Yes, a Docker image is available; use commands like `docker run` with volume mounts to convert collections inside containers, as detailed in the Docker Usage section for consistent execution.

postman-to-k6

What is postman-to-k6?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions