Runscope API Monitoring    Learn More →

Posts filtered by category: testing

Building a Steam Powered IoT API with Thingsboard

Building a Steam Powered IoT API with Thingsboard

By Joshua Curry on .

The project began late at night, as all good steam projects should. I had been thinking about some of the projects I’ve built with microcomputers like the Raspberry Pi and wanted to vault them out of the bland novelty of blinking and beeping boxes.

I have a model steam engine I inherited from a tinkering uncle and thought it would be a gas to try and make an IoT device out of it. I also have experience in API production and consumption, so I wanted it to be a relevant POC for devs trying to integrate the physical world with the virtual.

Bridging 300 years of technology seemed like an appropriate way...

Read More →

Categories: featured guest series, IoT, testing


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


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


Tutorial: Introduction to Monitoring SOAP APIs

Tutorial: Introduction to Monitoring SOAP APIs

By Heitor Tashiro Sergent on .

The SOAP vs. REST debate might have ended with REST as the clear winner in adoption for the most recent years, especially when we're talking about public APIs. However, SOAP APIs are still available and being used, especially in maintaining support for legacy systems, or in specific industries, such as financial and telecommunication services. Even big tech companies still have SOAP APIs available, such as PayPal, Flickr, and Salesforce.

Runscope supports testing any HTTP request, which includes making SOAP requests. In this tutorial, we're going to walk through how to test a SOAP API that returns geolocation information based on an IP address and validate its response using assertions and...

Read More →

Categories: tutorial, testing, monitoring, soap


How Trustpilot Tests and Monitors 200 Microservices

How Trustpilot Tests and Monitors 200 Microservices

By Heitor Tashiro Sergent on .

Trustpilot's journey with Runscope began back in 2015. They started off with our free trial plan, and have since grown to almost 5 million test runs a month. They were kind enough to chat with us about their experience, and how they transitioned from a single monolithic application, to a more efficient microservice architecture with over 200 microservices and hundreds of endpoints. 

Here's Dumitru Zavrotschi sharing their story...

Read More →

Categories: customers, microservices, monitoring, testing


6 Common API Errors

6 Common API Errors

By Heitor Tashiro Sergent on .

Have you ever used an API that returned an HTML error page instead of the JSON you expected, causing your code to blow up? What about receiving a 200 OK status code with a cryptic error message in your response?

Building an API can be as quick as serving fast food. Frameworks like Express, Flask, and Sinatra combined with Heroku or zeit's now help any developer have an API up and running in a few minutes.

However, building a truly secure, sturdy, hearty API, can take a little more work, just as a chef takes more time when crafting a great meal. You need great docs, clear and concise error messages, and to meet developers' expectations of...

Read More →

Categories: apis, debugging, microservices, monitoring, integrations, testing


Everything is going to be 200 OK®