Runscope Reviews

We use it to monitor the APIs. We always have them scheduled there.

As we have them 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.

We have it all monitored. Even 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 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.

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.

Also, 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. It's rare that this happens, but sometimes it does happen because the service loads are loading at the same time. What our tests were doing is creation, addition, and deletion. Before we deleted, this one service crossed the results of another one. And then we deleted the thing and broke another service. It was just a coincidence of the same millisecond, so one thing that could solve this would be if we could schedule the exact time that we want, or to schedule the order of service execution. That would be a good improvement.

No issues with stability.

No issues with scalability. It's fine.

Tech support has been pretty good. We had a problem. We accidentally deleted a bucket. We were trying to create a script and deleted a bucket. I needed to ask support to use the backup to get things up. Maybe a good feature would be to show this backup inside the tool, so end-users can just do backups by themselves.

We did use Postman but not for scheduling; just to do a quick check, we ran it from there. I don't know too many tools in the market, so it's hard to make a comparison. I think Postman does notifications and schedules stuff, but I don't know the price, so I don't know if it would be similar or totally different.

The setup was very nice. It was fine.

I think it's a good price. Once I asked my boss to approve it, he approved it immediately.

I would rate Runscope an eight out of 10 because it's still missing flexible scheduling, the exact time or the ability to sort the services the way we want them to run.

Our primary use case for this solution is API tests.

Since we are working with Runscope, we have a tool which is shareable between all the team members in a uniform standard. Now, each of us can easily run all our tests in a couple of minutes before deployment and all the team can see the results. We can receive an email and slack notifications if tests are failing/passing.

• Ability to schedule and compare the test suite results over time periods. 
• It has a relatively simple user experience. 
• Ability to copy tests suite between buckets. 
• Ability to add JS libraries. 
• Email and slack notifications. 
• Ability to run a large amount of tests simultaneously. 
• Revision option (to track changes). 
• Shared environment for tests.

• Ability to create code which runs before and after API tests. 
• The area of "initial script" is relatively small and incomplete related to code editors. 
• There are no regular features and validations for editor. 
• If triggering test bucket via trigger API, there is no option to see if the tests which were triggered passed or failed.

During the using period, we experienced several downtimes.

There are not many options for scalability.

The support is very good. They answering quickly and effectively.

We were using editors to create scripts and run them locally. This was unstable, not shareable, or a uniform solution. We were not able to run big amount of tests simultaneously and receive notifications.

The initial setup was pretty straightforward. The work is in the cloud, you have to set integration options and libraries, if needed, then start to work.

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

We did evaluate other solutions before choosing Runscope.

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.

API monitoring and testing.

Runscope is able to detect API layer issues in our production environment before our customers are able to.

Automatic scheduling of test execution. 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.

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.

No issues with scalability.

Tech support was more responsive prior to the acquisition by CA Technologies.

Previously used Postman. I needed the scheduling feature that Postman, at the time, did not have.

Setup was moderately straightforward.

Try it out and see if this product will work for you.