Postman vs Runscope comparison

"It's user-friendly. Anybody can learn it within five to seven minutes."

"It is simple, easy to use and a good tool."

"The solution collects scenarios and allows for testing SOAP API, REST API and API automation at the same time."

"It's easy to see different versions of responses."

"The API testing features are valuable."

"The interface and the different types of API methods you can use are the most valuable aspects of this solution."

"The environment variables are a valuable feature because I can easily switch them and see all the developments in different cycles and stages."

"In Postman, we have an option to directly import a call, make it a Postman collection, and execute it in a batch. This feature is very useful. It saves a lot of time. The manual effort is also reduced when we can just pick it in a Postman collection and then run and execute it to get the results."

"The schedule is definitely the most valuable. Also, being able to check the JSON attribute values is helpful. We always check the attributes. Finally, the notifications are helpful as well."

"We utilize modular tests based on environment variables. These have saved QA a lot of time when setting up our back-end automation."

"It is a cloud-based environment for building and executing tests, which allows me to focus on building, running, and reviewing test results."

"Environment initial variables allow our team to run tests against multiple environments on the fly."

"We love the fact that we can have our API tests run on a schedule as often as we need. We also take advantage of being able to set up different environment settings so that we can use the same test in our production, integration, and QA environments, easily. The ability to string together a number of API tests for a test suite is very important to us as well."

"It helps us verify that production deployments do not break the features our customers use."

"The feature of automatically executing tests at a predefined time interval is great as we can be continuously testing our end-points before and after builds are deployed."

"Valuable features include: Being able to add tests as sub-tests in a parent test for regression testing; notifications for tests that pass/fail; being able to customize expected results with assertions; being able to set tests to run daily."

"Postman does not have a check-in balance. Essentially what I mean by that is if there is something that is already configured on a particular device, it just overrides it without checking whether you really want to override it or not."

"It should be able to check the records and compare them to the regression testing more on the automation side."

"The solution could be more user-friendly."

"If there is any way to have a record and playback feature through UI, as we do in Selenium and IDEs such as Eclipse, it would be great."

"UI testing needs to be added to the solution."

"The tool needs to have a reporting feature."

"One of the features that is missing in Postman is reporting; it's very basic."

"I have recently noticed that, for some reason, I am not able to import collections in JSON. It is weird because I was able to do it before. When you create a new collection and documentation, in tests, you usually have to click Save. If you don't click Save, your collections don't sync with other devices, which is something I don't like. It is not clear for the users in a shared workspace, and I usually forget to click Save and end up losing all the collections that I created. I create a lot of routes, and clicking Save all the time isn't efficient. Instead of clicking Save all the time, there should be an option to save everything in one go."

"If you forget to set the default environment during test creation, you have to go through every test and make sure that it is set to the environment that you prefer if using shared environments. If there was an option to force all tests within a bucket into a specific environment with one click, this would save a lot of time."

"One thing that can be improved is the logging. Sometimes, when we have an error, we don't know how to find more information about the problem that has happened. Sometimes, it just returns something like "that gateway." More information would be a way to improve it."

"We would like to have an improved ability to share a set of tests across different environments (e.g., dev, stage, and prod)."

"I would like to see easier integration and display of test results so that the data could be shared via a dashboard within our company. (Some integration is possible, provided you use one of the supported platforms)."

"Navigation can be a little tricky when changing run environments and switching between test run results and editing the tests. It would be nice if you could switch the environment for all tests in a Bucket to run, rather than having to change each test environment."

"If triggering test bucket via trigger API, there is no option to see if the tests which were triggered passed or failed."

"Reliability. I would like to see more money invested in disaster recovery testing of the application. The product should be hosted across several AWS regions so if there are issues with an EC2 instance in a particular region, the whole application won't be affected. Once or twice a year there are issues with AWS that causes the reliability of the application to suffer."

"The initial setup included a lot of repetitive manual work."

"We are using its free version."

"I rate the price of Postman a four out of five."

"We use the open-source version. They introduced a new licensing model where your company must subscribe to their services if you're using it for business purposes. However, I think they charge too much if you're only using the basic features. It limits what your organization can do if you're not a paying customer."

"Postman is a free service."

"I am using the free option."

"Its price is moderate as compared to other competitors. The version that we are using is not open source, so it is not free."

"The solution's price is reasonable."

"The solution has a licensing fee which might be prohibitive."

"Having the different plans organized by team size, buckets, and requests per billing period works for our needs. Larger companies may need to take a close look at these elements."

"Pricing is fair."

"The price for the product is very reasonable for a team of more than four to five members."

"Runscope pricing is unbeatable"