Posted on Leave a comment


Get notifications for automated run

Make sure you open a schedule that runs automatically.

  1. Open tab “Notifications” .
  2. Check the box “Send Notifications”.
  3. Choose “failed runs” or “every run” in drop down menu.
  4. Check the box “Notify on Slack”.
  5. Insert a unique URL created with Incoming Webhooks in Slack (ex.
    Please notice: you need to open Slack settings to configure Incoming Webhooks in Slack and to create a unique Url. Check Slack installation instructions here

Posted on Leave a comment

Using schedules for automated runs

Run your tests automatically

Create a schedule to run one or several tests automatically at a certain time. A schedule can be run hourly, daily or weekly.

Setup a Schedule:

  1. Open an execution page.
  2. Click .
  3. Add tests to your new schedule.
  4. Open a schedule and rename it.
  5. Check the box “Run automatically”.
  6. Enter the time and frequency when Testup should run your tests.
Posted on Leave a comment

How to integrate tests into Gitlab CI/CD pipelines

This tutorial shows how you can easily run all your tests from a Gitlab pipeline. We assume that your current pipeline is already able to build and deploy your software. This tutorial contains the following steps to complete this task:

  1. Get your ApiKey from Testup to authenticate your Gitlab pipeline
  2. Insert the ApiKey into a secure space as a Gitlab variable.
  3. Extract the Id of your project
  4. Setup the Gitlab pipeline to run your tests
  5. Optional: Make temporary changes to the settings in your test

1) Get your ApiKey from Testup

Go to your Testup start page and click on the “Profile” tab. Find your ApiKey und the section “Api Keys”

2) Provide your ApiKey to Gitlab

Since the api key gives full access to your testup settings it should be provided to the Gitlab pipelines in a secure way. To do this open Gitlab and follow these steps:

  1. Open the project settings
  2. Open the CI/CD section
  3. Expand the Variables section
  4. Press “Add variable”

Once you successfully opened the add variable dialog you can provide your details as follows:

  1. Change your variable’s name to “TESTUP_APIKEY”
  2. Paste the Testup ApiKey into the value field
  3. Uncheck the “Protect variable” box (or alternatively protect your pipelines that should run your tests)
  4. Press “Add variable” to complete the setup

3) Find your Testup project Id

In this step you must find the numeric Id of the project containing your tests. For this step you navigate to your project in the browser, such that you see a domain that it has the form<projectId>?… Keep that project Id ready as you will need it in the next step.

4) Setup your Gitlab Pipeline

We assume that you already have a running pipeline that builds and deploys your project. Testup can only run your tests with access a deployed version of your software. Therefore, you need to add the end-to-end test as a final stage in your build pipeline. Go to your stages section and add e2e-test. Your file .gitlab-ci.yml will probably look something like this:

stages:          # List of stages for jobs, and their order of execution
  - build
  - unit-test
  - deploy
  - e2e-test     # Add this stage here

As a next step you add your end-to-end test step at the end of your pipline description. Your new pipeline step can be inserted as shown below. Don’t forget to provide the correct project Id.

Testup:   # Run this job after deployment completed successfully
  stage: e2e-test
  image: curlimages/curl
    PROJECT_ID: <YourProjectId>
    - URL="$PROJECT_ID/run/$CI_JOB_ID"
    - curl $URL -H Authorization:\ ApiKey-v1\ ${TESTUP_APIKEY} -s --retry 12
    - curl $URL -H Authorization:\ ApiKey-v1\ ${TESTUP_APIKEY} -s --fail

How exactly does this step work technically? First, it starts with an image that provides the “curl” command. Then it builds the url that triggers the start of the pipeline. This url contains the project id to run as well as the Gitlab job id to distinguish update requests from new runs. Following these preparations two curl commands are issued. The first calls Testup and retries until the test is either marked as failed or passed. Until ready the endpoint returns a 504 timeout code along with some early debug information. This first curl also makes sure that your pipeline’s debug messages contain useful information and a link to the corresponding resource in Testup. The second curl is necessary to make the pipeline fail if the tests failed.

Once your pipeline is set up you will see a debug message in your pipeline that looks something like this:

4) Optional: Provide additional settings to your test

Very often it is necessary to run your pipeline tests with other values than the ones used in interactive editing. Common cases are temporary domains or changing parameters for users, passwords etc. You can provide additional parameters in the message body of the curl. It is possible to replace urls and text contents that occur in your test. Your pipeline would then look like this:

Testup:   # Run this job after deployment completed successfully
  stage: e2e-test
  image: curlimages/curl
    PROJECT_ID: <YourProjectId>
    - URL="$PROJECT_ID/run/$CI_JOB_ID"
    - curl $URL 
      -H "Authorization:\ ApiKey-v1\ ${TESTUP_APIKEY}"
      -H "Content-Type: application/json"
      -s --retry 12
      --data '{
       "message": "Execution title shown in",
    - curl $URL -H Authorization:\ ApiKey-v1\ ${TESTUP_APIKEY} -s --fail

Posted on Leave a comment

How to handle randomly appearing content

Randomly appearing content such as popup windows shows up mostly due to the following reasons: unknown user for a website, deep scrolling or longer time on the webpage. In Editor, mode, you can control the flow depending on weather the pop up appears or not.

Make sure the pop up appears during test creation.

  1. Switch to mode.
  2. Click on .
  3. Draw an Anchor area around close button and play it.
  4. Add a conditional jump .
  5. Insert actions to close the popup content.
  6. Add actions below created #Tag to continue your test.

Please notice:

Next time when the popup content would not appear, the Robot will jump directly to the #Tag.

Posted on Leave a comment

Logins and Passwords

Your Website requires authentication

Enter Login and Password in URL of the website under test as follows:


  1. Open Test Settings.
  2. Enter URL, including your Login and Password;
  1. Click as a new test step.
  2. Enter URL, including your Login and Password.

Your Website shows Password dialog

Make sure you are in mode.
Make sure the entry field is active.

  1. Click to enter Login.
  2. Enter Login and press [ENTER] to confirm the action.
  3. Press [TAB].
  4. Click to enter Password.
  5. Enter Password and press [ENTER] to confirm the action.

Please notice

If your user name is an e-mail address, you will need to encode the @ symbol before you can include it in the URL. To do this, simply replace the “@” with “%40”.

Posted on Leave a comment

Conditional Jump

Conditional jump , enables you to control execution flow depending on true/false value in Clipboard Content. Conditional Jump is only possible to a certain place in Action List that is marked with #Tag.

Introduce a condition using or .
Make sure you are in mode.

  1. Click on .
  2. Type in Tag name to jump in case of false return.
  3. Press Enter and record the action.
  4. Replay the test to check the expected behaviour.
    Once the condition is met and Clipboard content returns a true result, false path will end. Test actions will continue playing.

Please Notice

Click to control execution flow if the value in Clipboard content is true.