Need advice about which tool to choose?Ask the StackShare community!
FitNesse vs Postman: What are the differences?
Introduction
FitNesse and Postman are two popular tools used for software testing and development. While both tools serve a similar purpose, there are key differences that set them apart.
Integration with different systems: FitNesse focuses on integration testing and is designed to work directly with the codebase, allowing developers to write tests in the same language as the application being tested. On the other hand, Postman is primarily used for testing APIs and web services, providing an intuitive interface to make HTTP requests and inspect responses.
Collaboration and documentation: FitNesse provides a wiki-based platform where teams can collaborate and document their tests, making it easier to share knowledge and maintain test suites. Additionally, FitNesse tests can be written using plain English, making it accessible to non-technical team members. In contrast, Postman offers features for team collaboration and documentation, such as shared workspaces and API documentation generation, but it does not provide the same level of flexibility and ease of use for non-technical users as FitNesse.
Test execution: FitNesse allows for the execution of tests directly within its wiki interface, providing immediate feedback and results. This makes it convenient for developers to quickly test their code changes during the development process. Meanwhile, Postman requires tests to be executed through its separate application, making it less integrated into the development workflow.
Test automation: FitNesse has built-in support for test automation, allowing developers to write scripts to automatically execute tests and integrate them into their continuous integration pipelines. Postman also supports test automation through the use of scripts written in JavaScript, but it requires additional setup and configuration compared to FitNesse.
Support for different technologies: FitNesse is mainly focused on testing software written in object-oriented languages, such as Java and .NET. It provides built-in support for these technologies, making it easier to write tests for applications built with these languages. Postman, on the other hand, is technology-agnostic and can be used to test any API or web service, regardless of the underlying technology stack.
Pricing and licensing: FitNesse is an open-source tool and is available for free, making it an attractive option for small teams or individuals with limited resources. Postman offers both free and paid versions, with the paid version providing additional features and support. This makes Postman a better choice for larger teams or organizations that require advanced functionality and dedicated support.
In summary, FitNesse and Postman differ in their focus on integration testing and API testing, collaboration and documentation capabilities, test execution and automation features, support for different technologies, and pricing/licensing models.
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 FitNesse
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 FitNesse
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