Running Performance tests using Nouvola

Once you have deployed your application to your staging / pre-production environment, you might want to run performance tests on your application using a third party tool.

Nouvola is a popular third-party service that offers real-world performance & load testing for web, mobile, API and IoT apps so developers, DevOps and engineering managers can release better code faster

You can automatically trigger your test suite authored in Nouvola, after your application has been deployed using Shippable. This tutorial demonstrates how to run Nouvola test plans using runSh jobs on a service you have already deployed.


  1. This tutorial executes a test plan on a NodeJS application, whose deployment is covered in this document. The test plan is a simple application availability test that loads the landing page of the app, using 2 virtual concurrent users.

  2. Define your test plan in Nouvola and note the Plan ID. test plan

Specify the Nouvola API key and test plan id in your shippable.yml file.

  1. Find your Nouvola API key using this document.
  2. Create a secure environment variable by going to your Subscription settings -> Encrypt. Secure API env key
  3. Copy the secure key to the clipboard by clicking on Copy.
  4. Specify the secure key and plan id in your shippable.yml file.

  - name: api
    type: params
      - test-api-nouvola
        NOUVOLA_PLAN_ID: "4609"
        #secure NOUVOLA_API_KEY environment variable
        secure: QbUdwdZzHSnFlKPxcsjJMp/qyICw4DPa2+VkqG9G42rYGCIAbecTVdIC933mljlJ1Z+OKhxk2zEevrczi7FxqLR+ts16AtvXHgRgwdmLLWmxX3trjfXDSWXOE5+GNHYmaZOQLm8qQjouogP8Kkx8njYj9Uut4ONaNZUsHvVroVSyfwiPktyKjQP8iEIzaV/Jb1wWwLHsDf1n4GaCcbm1VuloxoNuJkG5VftcnMqULWyN9YeZTxQ43PiflTWFqBHV9hPpbVU+N5Jt1kGfhBlj6FdiIiB69KrXXd/ooBwz7UuuNgPyXEjZtUC0tp0CzZlovnNPBdrMRiZ/yE1ZgbuDbQ==
  1. You can find the Plan ID in the test plan page, in parenthesis (xxx), next to the test Name in the Nouvola dashboard.
  2. We are going to call a script that executes Nouvola API calls in our runSh job. In order to do so, we need to also specify our repository as a resource in the shippable.yml file.
  # GitHub repo holding scripts to be used in runsh pipeline job
  - name: github-repo
    type: gitRepo
    integration: dr-github # replace with your GitHub integration name
      sourceName: devops-recipes/test-api-nouvola # replace with source code location (e.g. GitHub) where you cloned this sample project
      branch: master
      - test-api-nouvola

Call the Nouvola API to execute your test plan in your shippable.yml file.


# jobs for the Nouvola sample application


# add pipeline job
# Run API tests on Nouvola cloud
  - name: test-api-nouvola-run-tests
    type: runSh
      - IN: api
      - IN: github-repo
        switch: off
      - TASK:
        #key value pairs declared in PARAMS resources are exported as
        - script: echo "API KEY "$API_PARAMS_NOUVOLA_API_KEY
        - script: echo "PLAN ID "$API_PARAMS_NOUVOLA_PLAN_ID
        - script: . $GITHUBREPO_PATH/gitRepo/
      - test-api-nouvola

The script, which you can find in the sample below, performs API calls on Nouvola to queue and poll the test plan execution. It uses the environment variables from the params resources.

After you add your repository to the pipeline and run the test-api-nouvola-run-tests job, you will see something like this in your console -


The build will complete when status transitions from Waiting->Starting->Working->Analyzing->Emailed.

Connecting the runSh job to your deploy job in the pipeline

If you have created a pipeline with a deploy job and want to run these tests after your deploy job completes, there is a simple way to connect your runSh job to your deploy job. We will connect the deploy job specified in ECS deploy using an OUT directive.

  - name: deploy-ecs-basic-deploy
    type: deploy
      - IN: deploy-ecs-basic-manifest
      - IN: deploy-ecs-basic-ecs-cluster
      - OUT: test-api-nouvola-run-tests

Sample project

We have a working sample for the scenario described here. Instructions to run this sample are in the file.

We invite you to explore the full sample in this GitHub repository and clone it to test drive it.