Postman vs Runscope comparison

"The user interface is very easy to learn and use, and it is a lightweight application."

"We use it for REST API testing. Feature-wise, it is pretty lightweight. It is pretty fast, and we don't have to do a lot of things. We can just simply go and post our endpoint, and it gives different kinds of authorizations. We usually use authentication 2.0, which is the most common industry practice. So, it has the support for authorization through 2.0."

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

"Overall rating: Ten out of ten."

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

"The most valuable features of the solution are that it is easy to use and user-friendly."

"Postman uses the DRY framework of JavaScript and that framework is easy and a good way to put assertions on responses."

"The solution has helped us very well in testing endpoint URLs."

"It is a relatively reliable tool for running big amounts of API tests, which you can schedule to run periodically, as the product is very good."

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

"Tests are per-step configurable with script capabilities and support for token-based authentication using variables. Configurable test frequency and integration with both Slack and PagerDuty for alerting our DevOps team are also important. General use of the dashboard by multiple team members is also valuable."

"As we have the APIs scheduled, we use the notifications. We know the exact moment it is breaking something that might impact the customer system, that might result in a feature not working. We know "in advance" and we can fix it before the customer notices. It helps us to be more proactive."

"When it's a problem on our side, the server is down, or there is a lack of memory, the first thing to break is the API, because the calls can't be processed. So we know exactly at that moment because we receive notifications, and we can take action. It doesn't only notify us of the type problem, but it also links it to our servers."

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

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

"It uses JavaScript which is easy."

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

"I would like to have a code snippet where I can write a code and for the responses of the endpoints to be validated using my custom business conditions."

"Initially, the setup is a little bit complex. Whenever a user comes to Postman for the first time, it is just a bit complex since they do not know where to start and what is the structure."

"The tool needs to have a reporting feature."

"The reporting could be better. It should give you a detailed PDF report after you run a test."

"Postman quality assurance could improve when doing tests."

"We do the implementation of Postman and give support. We had to use two engineers for the implementation, one senior and one junior for the process."

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

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

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

"the built-in editor for the scripts can be improved a lot. Instead of making such a basic editor, maybe include a little more so it is easier to look at things and debug."

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

"File upload is a big part of the products that we test. The lack of file upload in Runscope requires us to still use UI (Selenium) automated tests for these scenarios."

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

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

"Unlike APIs, the solution does not require a license."

"Postman is a free service."

"The solution's price is reasonable."

"Postman is an open-source product. It is free to download from Google."

"This solution offers a free version."

"We are using the free version that is available."

"The solution is open-source and free."

"The solution is free for individuals, but for companies that use it across the organization, you have to pay per user."

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

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