Runscope API Monitoring    Learn More →

Introducing Runscope Environments: Bringing Teams Together Across the Entire API Development & Operations Lifecycle

By Neil Mansilla on .

Since we started Runscope just over two years ago, we’ve been committed to creating a suite of tools that support the modern development lifecycle. API architects, app developers, QA testers, QA engineers and DevOps engineers rely on Runscope for in-depth API monitoring and testing, and our goal is to serve any and all teams that publish and consume APIs.

Different teams use Runscope for testing across local dev, staging and production environments, and collaboration and deployments should be seamless for everyone. As you’ve adopted Runscope into your automated workflows, you’ve given us valuable feedback on how your needs are evolving and how we can better serve them. One of the key challenges when working across teams is managing configuration. We've listened to your feedback, and today we're addressing one of our top feature requests: support for multi-environment testing.

Now Available: Runscope API Test Environments

We’re thrilled to announce that you can now reuse Runscope API tests across multiple environments—from local dev to staging to production. By adding the option to include different environments in the same API test, Runscope complements the varied teams and continuous integration and deployment processes you use today. 

An environment is a group of configuration settings (initial variables, locations, notifications, integrations, etc.) that are used when running a test. Environments can be particularly beneficial in cases in which you need to repurpose the same set of test steps with different configurations, e.g. executing the same test against the local dev version of an API in addition to the live production version. There are two types of environments you can define in Runscope: test-specific environments and shared environments. The former can be applied to a single test; the latter can be applied across multiple tests. We’ll explore a common use case for environments in the next section. 

How Do I Use Environments?

The moment you create a Runscope test, you’ll already be using environments. Every test has at least one environment, and you can add as many test-specific environments as you’d like (like dev, staging, prod, etc.).

1. Create a test

In this example, we create a multi-step API test called Potions Inventory that verifies that our methods for fetching, creating and deleting items are working properly. Notice that we’re using a placeholder variable {{baseUrl}} in the endpoint rather than a static URL. Next, we fill in that value when we define our environments.

2. Add new environments and apply them to test runs

We create three test-specific environments: Local Dev, Staging and Production. In this example, the primary difference between the environments is the {{baseUrl}} initial variable, which is used in all of the endpoints of our requests.

We also set different test locations for each of the test-specific environments. For instance, in the Local Dev environment, only the on-premises testing agent (running on a laptop) is selected. For the Staging environment, tests are executed from one location in the cloud. We use the Production environment for scheduled monitoring and select multiple locations in the cloud from where the tests will be executed.

Setting up test schedules is even simpler with the introduction of environments. Click Schedule, then select the environment and frequency. In this example, we set up a scheduled test run using the Production test-level environment repeating on a one-minute interval. Then, run your tests!

Free Webinar to Learn More

There are so many new and useful features to cover related to environments. Register to attend a free live webinar on how to get started using Runscope environments on Thursday, August 6 at 10 a.m. PT. [UPDATE: This webinar has passed, but you can view the recording.] We’ll cover more use cases and invite you to bring questions! You can also read the documentation and contact our support team.

Healthy APIs require teams to work together throughout the entire development and deployment lifecycle. With Runscope environments, your dev, QA and ops teams can work together on a single set tests verifying critical functionality and uptime performance. To start building better APIs with your entire team, sign up for your free Runscope account.

Categories: announcements, product, howto, testing

Everything is going to be 200 OK®