Clik here to view.
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 how to:
- Generate a Runscope API access token
- Get your tests Trigger URL
- Set up your environment variables in CircleCI
- Run the Python script as part of your test commands
Let's get started!
Setting up the Runscope Python script
You can find the sample script in our GitHub:
The two files we're interested are requirements.txt and app.py. For this tutorial, I'm just going to work with the raw links from our GitHub repository.
If you're integrating this into your project, I highly recommend either forking it to your own repository, or adding these files to a separate folder. That way, you can prevent your build from breaking in case there's an update to the repository.
Getting your Runscope variables
Trigger URL
When running this script from the command line you can pass one parameter to it, which is a Runscope Trigger URL. If you want to run a single test, you can find its trigger URL under your environment settings:
Image may be NSFW.Clik here to view.
If you want to run all the tests in a bucket, you can find a separate trigger URL in your bucket settings:
Image may be NSFW.Clik here to view.
Image may be NSFW.Clik here to view.
Generating Your Runscope API Key
We need a Runscope personal access token to interact with the Runscope API and retrieve the results from our test run.
To get your access token, head over to your account's application tab, and click on Create Application. In the next screen, give your application a name, website URL, and callback URL. You can use dummy URLs if you're just using this app for your CI integration (e.g. http://example.org):
Clik here to view.
Click on Create Application to finish the process. Then, scroll down to the bottom of your new application page and copy the personal access token value. We're going to use that in our next step:
Image may be NSFW.Clik here to view.
Integrating with CircleCI
In your CircleCI account, select the Build tab on the left-hand side menu, and click on the gear icon next to the project you want to integrate with Runscope to open its settings:
Image may be NSFW.Clik here to view.
On the left-hand side Settings menu, click on Environment Variables under Build Settings, then click on Add Variable. We only need to add one environment variable here named RUNSCOPE_ACCESS_TOKEN. Paste the access token that you copied in our previous step under Value, and click on Add Variable:
Image may be NSFW.Clik here to view.
Now, let's go to Dependency Commands under the Test Commands menu.
The CircleCI environment already comes with python and pip pre-installed. The first thing we need to do is make sure the necessary packages for the script are installed. Add the following command to your Pre-dependency commands window:
pip install -r https://raw.githubusercontent.com/Runscope/python-trigger-sample/master/requirements.txt
Note: Remember to change the requirements URL above to your fork or local file.
Next, I'm going to add another command just below it to download our app.py file (you can skip this step if you copied the file to your project):
wget https://raw.githubusercontent.com/Runscope/python-trigger-sample/master/app.pyImage may be NSFW.
Clik here to view.
For the final step, let's head to Test Commands under the Test Commands menu. In the Post-test commands window, we can run our app.py script. It takes one parameter, which is the Trigger URL you copied at the beginning of this tutorial. So we can just run the command as:
python app.py https://api.runscope.com/radar/ba6e5157-29bc-4dae-96aa-221ffc559361/trigger?runscope_environment=84fcfb03-cfe4-412e-b460-1bca75b0aefa
Note: Remember to use the correct directory for app.py if you copied it to a folder inside your project.
Image may be NSFW.Clik here to view.
Continuous Integration Complete
In your next build runs, you should be able to see an extra step running the Python script, and hopefully returning a green checkmark ✅:
Image may be NSFW.Clik here to view.
With Runscope integrated into your CI process, we hope that you have even more confidence in your builds and that your APIs will be 200 OK.
We used CircleCI in this tutorial, but these instructions should also apply to other CI providers as well (check our Codeship tutorial and our Jenkins plugin). If you need any help with those, please reach out to our awesome support team.
Are you integrating Runscope in your build process? If so, we'd love to hear how you're doing it, just reach out to us via email or on Twitter.