We have been able to set up regression tests that cover everything we need to monitor. We then set them to run automatically and forget about them. We are notified whether they pass/fail, and have been able to catch issues quickly when changes were made to our methods.

It has allowed us to go from no API tests to scheduled, automated tests integrated with PagerDuty in a few months. I was able to do this without having to hire a QA Developer. Existing manual QA testers were able to learn simple JavaScript and Runscope UI. Regression tests were executed in minutes instead of days.

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

Runscope allows our QA team to spend less time on our API smoke test during releases.

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.

Runscope has also helped to expose subtle network latency or routing issues with components managed by our cloud provider.

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.

It helps make sure that the program running the production server hasn't crashed without anybody knowing. Runscope makes sure that it runs properly and, if it does crash, something happens. It sends an email. Then, with Slack, we can notify somebody that something is not right.

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.

It speeds up production deployment.

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

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.