Beta Features

We have moved

This is a legacy version of Copado Robotic Testing help. This page will not be updated anymore.

See for up-to-date documentation.

Beta features give end users an opportunity to get familiar and give feedback on forthcoming features. Since beta features might not yet be on final form & production quality, they are off by default. Users can enable beta features when needed.

This section contains a short description of all features under "beta features" toggle.

Many of latest (beta) features only work with Kubernetes based runners. If you want to use them and are still using Jenkins based runner, please contact Copado Robotic Testing Support

Enabling Beta Features

  1. To enable beta features, navigate to your profile by clicking your avatar icon and then select Profile:

Profile menu

  1. Toggle the "beta feature" switch to On.

Beta features toggle

Beta features are now enabled for your user account.

Robot image selection - versions

New Robot

To enable image using different versions of browsers/drivers etc. when creating a new robot, follow the steps below:

  1. Follow instructions for adding a new robot

  2. If "beta features" are enabled, you will have additional settings / configuration options under Advanced options

  3. Click Show advanced options

Show advanced options

  1. Expand Robot versions dropdown

  2. Select a robot version that contains the version you want

Robot versions

Existing Robot

To enable different robot image for an existing robot, follow the steps below:

  1. Click Edit button on your robot

Edit robot

  1. Go to Advanced options

  2. Expand Robot versions dropdown

  3. Select a robot version that contains the version you need

Robot versions

Test Case Duration Change Analysis

Test case duration change analysis / performance change detection can be enabled for each suite individually. This feature tracks the duration of your test cases and individual steps, and warns you if there’s a considerable change. This information can be used to track down possible performance or configuration issues.

You can enable test case duration change analysis as follows:

  1. Click Edit icon on your test suite

Edit suite

  1. Under Analytics section, check Test case duration change detection

Enable test case duration change detection

After enabling this feature you need ~20+ runs for Copado Robotic Testing to get reliable baseline for test case duration.

Once Copado Robotic Testing detects significant change in test case duration, you would see a warning icon(s) like this:

Warning: duration change

Test Data API

Test Data API enables providing test data in Excel or CSV format. This is useful, when you want to use the same test cases or test suites with different data. Common examples could be doing localization testing with different languages or running the same tests using different product id’s etc.

Variating data on individual test cases

Prepare your Excel/CSV file.

Create an Excel file with data. You should have variable names either in first column or first row.

Variables do not need to contain $, { or } characters in Excel/CSV, but they are needed in test script. In Excel you can either include them or leave them out.
Table 1. Example: Variables in first row
* Test Cases * username password

Wrong email valid pw


Correct email, wrong pw


Wrong email, wrong pw


Table 2. Example: Variables in first column

* Test Cases *

Wrong email valid pw

Correct email, wrong pw

Wrong email, wrong pw






Upload your Excel/CSV to Copado Robotic Testing

  1. Use the "Upload test data set" button to upload data

Test Data Upload Icon

  1. Click [Choose File] and select your Excel/CSV file

  2. Choose if variables are in first row or column in your Excel/CSV. Click [Next]

Variables selection

  1. Select "Send to data API" anc click [Send]

Send to data API

  1. Your Excel/CSV file will be analyzed and if format is correct, an example test case template will be provided

Template test case

Prepare your test case

Create your test case implementing the steps as needed. Use the variable names in excel, but in Robot FW format (i.e. password in Excel would be ${password} in your test script). Note that you should add a keyword that implements the test case into *** Settings *** section of the script header. The main difference here is that test case just calls a "template testcase", which is defined in *** Keywords *** section

Running tests

Once you have uploaded data set and created your test case, you can run your test suite/case normally using Copado Robotic Testing. Instead of running just one case with static data, Copado Robotic Testing dynamically creates own test case for each dataset (row or colum). So with the above example data you would get 3 test cases, all with different data.


Variating data on whole test suites

To variate whole suite Prepare your Excel/CSV file. and upload it as when variating one test case only.

Create your test suite normally. Test suites can have one or many test cases.

The Test template which was needed when variating one test case is not needed here. Test Data API just reads variable data from Excel/CSV file. Also test implementation does not need to be under a keyword.

When running the suite, select which row/column is being used. This is done by selecting a data set/key, which is the first row or column in your excel. For example, with this kind of excel:

Table 3. Example: Data set / key







Log in

Kirjaudu sisään

Logga in





…​you have 3 data sets: EN, FI and SE. Data set/key can be selected in the Test data section. Here we would run this particular test suite with FI (=Finnish) translations.

Dataset/key selection

Once your data set is selected, just run the test suite normally.

You can create multiple pre-defined suite instances using different datasets/keys.

QConnect Dev

QConnect Dev enables local development and debugging of your Copado Robotic Testing scripts, right from your local editor.


  • On-premise development add-on must be enabled

  • QConnect Dev installation package must be installed

  • QEditor add-in for Visual Studio Code must be installed

QConnect Dev installation

Contact Support in order to enable On-premise development add-on for your account. Once it’s enabled, QConnect Dev installation package can be found from your profile page. To get there, click your profile icon and select "Profile" from the menu:


On the profile page, you should see download button for QConnect Dev installation package:

On-premise add-on

Install it and continue to Visual Studio code QEditor add-on installation.

QEditor for VS Code installation

QEditor extension for Visual Studio Code can be installed directly from Visual Studio Code Marketplace


by going to "Extensions" tab on Visual Studio Code and searching for "QEditor". Click install on the extension.

  1. Create a new Personal Access Key in Copado Robotic Testing following the instructions Personal Access Keys.

  2. Set Access Key

Set Access Key

If you can’t see the "Set Access Key" dialog, open a .robot file to editor and select task Set Copado Robotic Testing Access Key. Tasks can be found from menu Help  Show All Commands or using shortcut Ctrl+Shift+P.

Task: Set Access Key

Using QConnect Dev


Test case can be run locally just by clicking "Debug" annotation on top of the test case name:

Debug annotation

Clicking this link will run test case on local machine. Once the run has finalized, html logs will open in new browser window automatically.

Using terminal

Test can also be run from a console, exactly as any other robot framework tests. To open QConnect Dev Console, click it’s icon from the top right corner of Visual Studio code:

QConnect Dev Console icon

A new terminal will open. With this terminal you can run selected tests, tags, give variables, install additional packages etc.

QConnect Dev Terminal

Test logs can be found in "%LOCALAPPDATA%\Copado\QConnect\dev\output\log.html"

Intro to QConnect Dev video

Please watch a walkthrough of QConnect Dev installation and usage below.

Introduction to QConnect Dev

Using customized Python packages in QConnect Dev

QConnect comes with Robot Framework libraries required for all common web, desktop, and mobile testing. For special needs, QConnect Dev also supports development of tests that rely on custom Python packages. This support builds on Python virtual environments and the pip tool.

Managing your Python packages

QConnect Dev automatically sets up a virtual environment used in all QConnect Dev runs. Initially the virtual environment contains nothing but packages inherited from the QConnect installation.

To manage the virtual environment contents, use the QConnect Console command line. First open any .robot file in Visual Studio Code, then run the QConnect Console command in the VS Code command palette. In QConnect Console, the virtual environment is automatically activated, so commands such as "python", "pip", and "robot" operate within the virtual environment.

  • To install a Python package into the virtual environment, use pip install.

  • To view which packages you have installed, run pip freeze --local.

  • To view all packages, both those in the virtual environment and those inherited from the QConnect installation, run pip freeze.

  • To uninstall packages, use pip uninstall. Packages inherited from QConnect itself will not be uninstalled.

  • If you need to reset the virtual environment, delete the virtual environment directory and reopen QConnect Console. A new virtual environment is created automatically at the same location when QConnect Dev starts. The path to the directory is printed when QConnect Console starts, and is also stored in the environment variable VIRTUAL_ENV in QConnect Console.

The same virtual environment will be used by both QConnect Dev debug runs and QConnect Console. If you have several test suites in different directories, they will all use the same virtual environment. Any requirements.txt files in the test suites are not taken into account in QConnect Dev.

If you also run QConnect Agent to execute tests, note that QConnect Agent runs are not affected by the QConnect Dev virtual environment.

The QConnect Dev virtual environment is kept as it is when uninstalling or upgrading either QEditor or QConnect, so you can continue using QConnect Dev with your custom packages after the upgrade. However, if the new version of QConnect comes with a different version of Python, then it cannot use the existing virtual environment, and QConnect Dev will create a new virtual environment at a new directory.