Need advice about which tool to choose?Ask the StackShare community!
Newman vs Postman: What are the differences?
Key Differences between Newman and Postman
1. Testing platform: Postman is primarily a testing platform for API development and testing, providing a user-friendly interface for creating, managing, and executing API requests. Newman, on the other hand, is a command-line collection runner for Postman, allowing users to run Postman collections using scripts or integration with continuous integration servers.
2. User interface: Postman offers a comprehensive user interface with features like request builder, response viewer, test editor, and collaborative tools for team collaboration. Newman, being a command-line tool, does not have a graphical user interface and is focused solely on running collections using commands.
3. Automation capability: Postman allows users to write test scripts using JavaScript to automate the testing process. It offers a robust scripting environment with features like variables, environment management, pre and post-request scripts, and assertions. Newman is designed specifically for automation purposes and can be integrated into CI/CD pipelines for running Postman collections programmatically.
4. Command-line interface: While Postman primarily relies on its graphical user interface, Newman allows users to run collections through the command-line interface. This command-line interface provides more flexibility, enabling automation and integration with other tools and systems.
5. Continuous Integration/Continuous Delivery (CI/CD) integration: Postman provides integration with popular CI/CD platforms like Jenkins, Travis CI, and TeamCity through plugins and extensions. Newman, being a command-line tool, can be easily integrated into CI/CD pipelines using shell scripts or other methods.
6. Team collaboration: Postman offers collaboration features like team workspaces, shared collections, version control, and history tracking, allowing multiple users to work on API development and testing together. Newman, being focused on automation, does not include these collaboration features and is more suited for individual test execution.
In summary, Postman is a comprehensive API testing platform with a graphical user interface, collaboration features, and the ability to run collections through the interface. Newman, on the other hand, is a command-line tool specifically designed for automation and integration with CI/CD pipelines, providing more flexibility and scalability for running Postman collections programmatically.
From a StackShare Community member: "I just started working for a start-up and we are in desperate need of better documentation for our API. Currently our API docs is in a README.md file. We are evaluating Postman and Swagger UI. Since there are many options and I was wondering what other StackSharers would recommend?"
I use Postman because of the ease of team-management, using workspaces and teams, runner, collections, environment variables, test-scripts (post execution), variable management (pre and post execution), folders (inside collections, for better management of APIs), newman, easy-ci-integration (and probably a few more things that I am not able to recall right now).
I use Swagger UI because it's an easy tool for end-consumers to visualize and test our APIs. It focuses on that ! And it's directly embedded and delivered with the APIs. Postman's built-in tools aren't bad, but their main focus isn't the documentation and also, they are hosted outside the project.
I recommend Postman because it's easy to use with history option. Also, it has very great features like runner, collections, test scripts runners, defining environment variables and simple exporting and importing data.
Postman supports automation and organization in a way that Insomnia just doesn't. Admittedly, Insomnia makes it slightly easy to query the data that you get back (in a very MongoDB-esque query language) but Postman sets you up to develop the code that you would use in development/testing right in the editor.
Pros of Newman
Pros of Postman
- Easy to use490
- Great tool369
- Makes developing rest api's easy peasy276
- Easy setup, looks good156
- The best api workflow out there144
- It's the best53
- History feature53
- Adds real value to my workflow44
- Great interface that magically predicts your needs43
- The best in class app35
- Can save and share script12
- Fully featured without looking cluttered10
- Collections8
- Option to run scrips8
- Global/Environment Variables8
- Shareable Collections7
- Dead simple and useful. Excellent7
- Dark theme easy on the eyes7
- Awesome customer support6
- Great integration with newman6
- Documentation5
- Simple5
- The test script is useful5
- Saves responses4
- This has simplified my testing significantly4
- Makes testing API's as easy as 1,2,34
- Easy as pie4
- API-network3
- I'd recommend it to everyone who works with apis3
- Mocking API calls with predefined response3
- Now supports GraphQL2
- Postman Runner CI Integration2
- Easy to setup, test and provides test storage2
- Continuous integration using newman2
- Pre-request Script and Test attributes are invaluable2
- Runner2
- Graph2
- <a href="http://fixbit.com/">useful tool</a>1
Sign up to add or upvote prosMake informed product decisions
Cons of Newman
Cons of Postman
- Stores credentials in HTTP10
- Bloated features and UI9
- Cumbersome to switch authentication tokens8
- Poor GraphQL support7
- Expensive5
- Not free after 5 users3
- Can't prompt for per-request variables3
- Import swagger1
- Support websocket1
- Import curl1