Postman vs Runscope comparison

"The user-interface is very good."

"The variables part is good. We can easily define the variables and we don't have to manually do a change every time, it gets automatically updated."

"Postman allows you to incorporate and export the test cases we create. It enables me to share the test cases with my colleagues, so I don't have to copy them into an Excel sheet. Postman lets me export the dataset and share it with my team. They can use my test case for their testing."

"Simple to use and you can easily store your projects."

"It helps me to test APIs independently. It also supports hosting."

"Overall rating: Ten out of ten."

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

"It is easy and simple to use and install. It is compatible with Linux, Mac or Windows."

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

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

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

"It uses JavaScript which is easy."

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

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

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

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

"I would like to see more integrations with other platforms."

"Integration should be improved with our continuation system because we use Azure DevOps separately."

"The performance needs to be improved."

"One thing which Postman needs to improve is the documentation. The documentation of Postman is not that great when compared to other tools."

"Postman needs more advanced data-driven testing."

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

"The solution is quite complex partly because the UI needs simplification."

"One area that could be better is collection management."

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

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

"The user interface requires a lot of clicking around."

"We definitely make use of historical test results, especially when tracking more difficult issues such as timeouts. Per our test frequency (15 minutes) we often need to go back further than the last 100 test runs. We are aware that results further back in time are available through the Runscope API, however, it would be great if the dashboard allowed easy access to a larger amount of historical data."

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

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

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

"I use the tool's free version."

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

"I rate the product's price a nine or ten on a scale of one to ten, where one is cheap, and ten is very expensive. Postman is an expensive tool for Turkey."

"It is free."

"This tool is open-source and free to download and use."

"The solution's price is reasonable."

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

"Postman is a free service."

"Runscope pricing is unbeatable"

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

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