Runscope Reviews

We use it for doing smoke tests in production and testing in QA and in team environments.

It speeds up production deployment.

Pre-request Scripts and Post-response Scripts are very handy. Instead of adding a bulk of assertions to those associated test cases one by one, I can easily just write scripts, then copy and paste them into my test cases. This really saves me a lot of time on debugging and revising.

The documentation of Runscope needs to be improved. For instance, there is very much a lack of examples in the documentation. It is a bit difficult for beginners and intermediate users to get started quickly or to go deeper when creating test cases.

All my test cases failed when Runscope did a security patch a few months ago. That was the first time I found the stability wasn't great. Otherwise, it has been doing fine.

I have experienced no issues with scalability.

I have not had to contact tech support yet.

We had a previous solution, but Runscope has a better user interface and is easy to set up, so that is why we switched.

The initial setup is pretty straightforward.

I am not aware of the pricing and licensing as these topics are not part of my job.

Ask for more examples in the documentation.

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.

We use Runscope to test our API endpoints for our product, both on-demand and via a schedule.

Not only does Runscope allow us to keep our tests organized and available to everyone on our team, but it also alerts us when tests fail, via integration with Slack, so that we can address bugs that have been introduced.

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

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.

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

We have rarely seen any issues and have never seen an outage with Runscope's servers. Just make sure the agent is run on the proper hardware.

We are not limited in the number of tests that we run, nor the frequency, provided that we stay within our contracted rate. It is easy to manage that information.

We have had good success with tech support, especially when we were getting started. They are knowledgable and will help you all the way through your process until you understand the solution to your problem.

We have used Postman quite a bit, but Runscope makes it easier to group tests together in a logical way. In addition, being able to run tests on a schedule and make them available to everyone on a team is great.

Easy setup, easy to make your first tests. There is a bit of a learning curve when you are trying to decide how to group tests and use variables, but nothing that their tech team isn't able to help you through.

Pricing is very reasonable and is easy to pay when you are supporting a team of engineers.

We did not evaluate other options, other than continuing to use Postman for our API testing.

Tests can be brittle, so make sure you include checks to validate data and variables that you are using.