• 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
• The intuitive user interface that makes it easy to set up everything without a programming background

It is a cloud-based environment for building and executing tests, which allows me to focus on building, running, and reviewing test results. I do not have to waste time managing development environments on local machines. Being cloud-based, I can check the status on the test results from anywhere on any device. I am not constrained by a physical machine where the tests are running.

We have the ability to populate environment variables using scripts. This allows us to keep the configuration mostly dynamic and avoid a lot of manual updates when something changes. 

Schedules are a great way to have repetitive checks against the environment.

Environment initial variables: These allow our team to run tests against multiple environments on the fly. 

We utilize modular tests based on environment variables. These have saved QA a lot of time when setting up our back-end automation.

API monitoring where specific tests are designed to emulate production data-flows through our pipelines. Tests are per-step configurable with script capabilities and support for token-based authentication using variables. Configurable test frequency and integration with both Slack and PagerDuty for alerting our DevOps team are also important. General use of the dashboard by multiple team members is also valuable.

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.

It uses JavaScript which is easy.

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

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.

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.

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