Runscope API Monitoring    Learn More →

Posts filtered by category: integrations

Tutorial: Integrating Runscope with New Relic Insights

Tutorial: Integrating Runscope with New Relic Insights

By Heitor Tashiro Sergent on .

New Relic Insights is a real-time analytics platform that collects event and metric data from other New Relic products, and also third-party integrations. By connecting New Relic Insights with Runscope API monitoring, you can collect metrics from your API tests and transform them into actionable insights about your applications.

Connecting Your Accounts

We need two get two variables from New Relic to integrate it with Runscope: an Account ID, and Insert Key...

Read More →

Categories: tutorial, monitoring, integrations, howto


Tutorial: Continuous Integration with CircleCI and Runscope API Tests

Tutorial: Continuous Integration with CircleCI and Runscope API Tests

By Heitor Tashiro Sergent on .

CircleCI is a popular Continuous Integration and Delivery solution (used by Facebook, Kickstarter, Spotify), and integrating it with Runscope Trigger URL tests so you can run your Runscope API tests takes only a few minutes!
 
Runscope can be used by itself to monitor and test APIs, but it can also be used as part of your CI workflow. We have a sample Python script in our GitHub that can be used to trigger a set of tests in your Runscope account, and change the build status based on their results.
 
In this tutorial, we're going to show you how to use that script with CircleCI. We'll cover...

Read More →

Categories: code samples, tutorial, testing, integrations


3 Easy Steps to Cloud Operational Excellence

3 Easy Steps to Cloud Operational Excellence

By Bruce Wang on .

This is a guest post by Bruce Wang and Glen Semino from SYNQ, a video API built for developers. In this post, they explain the tools and processes they use to keep the company's API operations running smoothly, and share a real-world story of how they found an API bug before launching a new feature.

There are a lot of tools out there, and sometimes its hard to sift through them all. Here’s a simple guide to combine 3 tools, Runscope, PagerDuty and StatusPage to create a powerful cloud operational workflow that will give you peace of mind and clear visibility to your application for your customers and internal teams alike!

In case you’re not familiar with the tools, here’s a quick rundown:

  • Runscope — highly flexible API testing and monitoring service
  • PagerDuty — incident management system
  • StatusPage — Customer-facing API health status page

The workflow

It’s important to implement tools for specific purposes, and we wanted to integrate these 3 tools to help manage our operational process better. In the following examples, we’re going to show you how...

    Read More →

    Categories: apis, community, customers, debugging, howto, integrations, monitoring, tutorial


    Tutorial: Continuous Integration with Codeship and Runscope API Tests

    Tutorial: Continuous Integration with Codeship and Runscope API Tests

    By Heitor Tashiro Sergent on .

    A part of an engineer's toolbox is a good automation workflow. One of the tools in that box is a Continuous Integration provider, which can help teams prevent integration problems and improve quality control.

    Runscope can be used by itself on running and monitoring APIs, but it can also be used as part of your CI workflow. Our CEO, John Sheehan, created a sample Python script that can be used to trigger a set of tests in your Runscope account, and change the build status based on their results.

    In this tutorial, we're going to show you how to use that script with Codeship. We'll cover how...

    Read More →

    Categories: code samples, tutorial, testing, integrations


    Storing API Test Results to a Database with Eventn and Runscope

    Storing API Test Results to a Database with Eventn and Runscope

    By Eventn on .

    A common requirement for Runscope users is to save and analyze test results for alerting, building custom dashboards, and other analytical purposes. One way to do that is to pipe all your test results to an Amazon S3 bucket. But what if you want more flexibility in how you store the test results? Or if you want to filter and process the test result data before storing it? 

    Eventn is an HTTP microservices platform specifically designed for data processing and analytical workloads. You can use it to launch microservices, and each one you create provides a Node.js JavaScript function runtime that executes when an HTTP request is made.

    In this example, we will demonstrate how to call an Eventn microservice after each test completes and provide an example of saving the results to a database. We will also report on the data using SQL...

    Read More →

    Categories: howto, integrations, microservices


    Using Google Sheets and Runscope to Run API Tests with Multiple Variable Sets

    By Sam Aybar on .

    We frequently run into users who are looking to run an API test multiple times, using a variety of initial variables. For example, the user might be looking to:

    • Test the same request against a list of user ids, where user_id is the only query string parameter that changes.
    • Test edge cases for an API call. Passing a string to an endpoint that expects an int, or passing special characters to it, and making sure that nothing breaks.
      Share tests and results for multiple variable sets with other teammates for debugging.

    We have been able to accommodate this feature for a long time using our Batch Trigger URLs. With a GET request to a Batch Trigger URL, you can pass in an array of objects to specify initial variables for the test, and kick off up to 50 test runs at one time using different sets of variables.

    But what if you want an easier way to do this than to try to format an API request with a bunch of variables and build a JSON array with the different sets? And how do you match up your responses easily to the different sets of variables? What if we could make this easier?

    Read More →

    Categories: debugging, integrations, testing


    Everything is going to be 200 OK®