Lead QA Engineer at a financial services firm with 51-200 employees
Real User
Aug 19, 2018
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.
DevOps Engineer at a tech company with 1-10 employees
Real User
Jul 25, 2018
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.
Quality Analyst at a tech vendor with 10,001+ employees
Real User
Jul 25, 2018
Valuable features include: Being able to add tests as sub-tests in a parent test for regression testing;
notifications for tests that pass/fail; being able to customize expected results with assertions; being able to set tests to run daily.
Project Manager, QA Leader and Information Security Manager at a tech services company with 11-50 employees
Real User
Jun 6, 2018
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.
Test Engineer at a computer software company with 201-500 employees
Real User
May 28, 2018
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.
![Runscope [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/PNT6PqoKPXw9AHMYdimfVbN9.jpg?_a=BACAGSDL){kind=small}
It uses JavaScript which is easy.
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.
It is a cloud-based environment for building and executing tests, which allows me to focus on building, running, and reviewing test results.
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.
Valuable features include: Being able to add tests as sub-tests in a parent test for regression testing;
notifications for tests that pass/fail; being able to customize expected results with assertions; being able to set tests to run daily.
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 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.