Postman vs Runscope comparison

"What is most valuable for me is that we can create and share collections between the team members."

"It is easy to install, as well as to learn, particularly for new users, even if they are not developers."

"The API testing features are valuable."

"The most valuable feature is the user interface because it provides a clear space for the URL, headers, body, prerequisites, and tests."

"Postman helps to write pre-request scripts and make a collection out of each request. You don’t have to spend time writing or copying the requests. The solution lets you integrate multiple environments and their features. Either the tool’s pro or premium version lets you do the merge and pull request for the Git directly."

"The most valuable feature is that JavaScript can be included as tests."

"I can use multiple environments, which allows me to create environment variables for each endpoint."

"Good at simulating the API code from a fictitious client application to check API behavior."

"It uses JavaScript which is easy."

"We have the ability to populate environment variables using scripts. This allows us to keep the configuration mostly dynamic and avoid a lot of manual updates when something changes."

"You can run it off the cloud and against different data centers. That's one of the plus points for most people for this product, as opposed to some other solutions."

"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."

"It has a relatively simple user experience."

"This solution has improved our responsiveness to issues in both production and non-production environments. Through integration with Slack, our development and DevOps teams are quickly aware of issues related to new changes deployed to non-production environments, which tightens our feedback loop during testing. Through integration with PagerDuty, our DevOps resources are able to reduce the adverse impact of a given production issue."

"We can receive an email and slack notifications if tests are failing/passing."

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

"They should integrate the solution with one of the CRM solutions."

"I was not even aware that it was possible to automate tasks in Postman...Some features related to the automation of tasks need to be added to the solution."

"There is no support for the testing of the SOAP APIs."

"The request encryption could be one thing on which they can work a little bit. If we don't want to expose our production data but we still want to test our APIs on the production data, there should be a way to do that. It is not only with Postman. I think no tool in the market is doing that right now."

"The solution could be more user-friendly."

"It would be beneficial to expand functionality with additional testing options."

"Testing API is pretty straightforward in Postman, but it falls short when testing web services. For example, when we test web services, there is a visual component that we can import in SoapUI but not in Postman."

"The main improvement needed is better integration with test management and other tools to allow a common dashboard for all testing metrics and details."

"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."

"We would like to be able to select the actual time a test will run automatically. It appears that you can set up the automatic schedule, but the test runs based on the last time it ran and not a time you select. Since we want these tests to run in the middle of the night, it would be nice to be able to select that."

"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."

"We would like the ability to configure Runscope behavior when a given test has its schedule modified. That is, in a non-production environment, we often need to pause a test (either by removing it from the schedule or adjusting its frequency) and this results in the automatic kick-off of this test in all other environments. We would like the ability to simply pause a test for a specific shared environment without causing additional tests to be started."

"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."

"I've noticed, once or twice, when there were some updates pushed by Runscope, at times it didn't refresh the pages. I was running it, there were multiple tests running at the same time, and it didn't update the webpage I was looking at. So I had to refresh it manually. Occasionally, it still happens."

"Currently, we can only schedule to the nearest five minutes, one hour, two hours, etc. If we could set up the exact time that we want it to run, that would be good because sometimes we have one service that crosses another service."

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

"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."

"We are currently using the free version, but we have plans to buy a license."

"The solution has moderate pricing."

"The solution's price is reasonable."

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

"Postman is a free service."

"We do not pay any money for Postman."

"This solution offers a free version."

"Runscope pricing is unbeatable"

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

"Pricing is fair."

"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."