We use Postman for testing the functionality of REST APIs.
Within my organization, there were roughly five people using this solution, however, currently, I am the only person who is developing API testing tools.
We use Postman for testing the functionality of REST APIs.
Within my organization, there were roughly five people using this solution, however, currently, I am the only person who is developing API testing tools.
The user-interface is very good.
Actually, I received some errors regarding the testing of SOAP APIs. There's definitely some space for improving the user's experience. There needs to be more flexibility surrounding the testing of SOAP APIs. Currently, they are primarily based on JSON files — invest APIs actually.
I know that SOAP APIs are considered a little outdated but they're still in use. Unfortunately, because of this, I have to search for another solution that supports SOAP APIs, because Postman doesn't.
I have been using this solution for roughly one year.
It's a very stable solution. Regarding the overall stability of the application and the test results that achieved — It's really a good application.
We haven't really had to contact technical support. We have been able to solve nearly all issues via online forums.
It's not exactly complex, but I wouldn't say it's straightforward either.
The deployment process was very quick; I believe it took roughly one week to get it all set up. Still, not all test cases were set up within that time period.
All implementation was done by our in-house team.
As we only had 10 APIs to test, we used the free version.
Recently, I compared Postman with JMeter 12 for testing the load performance of the same APIs.
I would absolutely recommend this solution. It's one of the best solutions for testing REST APIs.
I had some great experiences using Postman, especially relating to REST APIs. Currently, I am in the process of learning about other tools suitable for API testing regarding SOAP APIs.
On a scale from one to ten, I would give Postman a rating of eight.
My primary use case is for API testing.
The interface and the different types of API methods you can use are the most valuable aspects of this solution.
The pricing should be adjusted for the Pro plan.
I have been using Postman for over a year.
It is quite stable. I don't use it quite extensively but for what I use it for it's quite stable.
At my current company there are around 2,000 users.
I haven't used technical support. The documentation is quite good. I use the Postman website and forums.
The deployment depends on what you are going to use it for. It can be simple and it can be complex at the same time.
When it comes to anything API related, I would recommend this solution. For anything API-related, it's perfect. REST API is the way to go and I would recommend Postman for it.
I would rate it an eight out of ten.
The pricing is the only improvement. Its competitors are quite pricey. But it would be nice if there were more options like annual, monthly or enterprise-level.
We are using Postman for our testing and checking our API response and validations.
What is most valuable for me is that we can create and share collections between the team members.
An area that needs some improvement would be to allow multiple windows with different collections to be open at the same time.
It only allows you to open one with the same collection.
If we open a new Postman window, it does not allow me to have the same collection as I had in the previous window. Allowing us to have replicas of the same collection open independently would be helpful.
I would like to see if it can incorporate Jenkins integrations.
I have been using Postman for five years.
It's a stable solution. It's running well.
Scalability is not for load testing.
You cannot scale vertically. You can only scale horizontally.
I haven't contacted technical support, but they do have good documentation available online.
We are using the free version that is available.
It's a good tool overall and quite stable.
It is mainly used for testing purposes, API responses, and validations.
I would rate this solution an eight out of ten.