If you were talking to someone whose organization is considering Runscope, what would you say?
How would you rate it and why? Any other tips or advice?
It's a pretty good product, as long as the price is okay for you.
Tests can be brittle, so make sure you include checks to validate data and variables that you are using.
Ask for more examples in the documentation.
* Prioritize tests. * Use environment variables. * Budget time to experiment with features before going full speed on test creation.
Create a DevOps team story to evaluate Runscope, which includes setup for all tests/buckets which will be used in your production environment. Exercise all use cases and outcomes, including integration with your desired tools (e.g. Slack, PagerDuty, etc.), and tune the available configurations as needed.
Create a script to populate tests from a config file. Store it in a source control and load/update it through the API. Doing things through the UI wastes a lot of time.
It's really easy to use and the documentation is extremely helpful if you get stuck on something. The product is flexible and allows you to set up variables and assertions in order to customize tests for your needs.
Runscope is the best option for REST API automation.
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.
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.
Try it out and see if this product will work for you.