Automated tests created in Test Modeller are executed on an execution server, either locally or remotely. This server can be created on any Windows machine that is accessible, for instance on your own machine, on a machine in your network, or as a virtual machine.

A remote server is generally preferable, as this means that you can submit execution jobs that run remotely, off screen. You can then carry on working on your machine while the tests execute. If you are working in a team, a remote server is especially preferable. If you set up a shared server on your local machine, the tests will execute on your machine whenever a member of your team submits a job.

Automated test jobs are run using a job engine that runs on the execution server. The server and job engine do not need to be switched on to fire off automation jobs, which will queue up when either or both are switched off. The jobs will then execute when the job engine is next turned on.

Two tasks must therefore be performed before automated test jobs can be executed:

  1. The server must be set up. This is a one off task for each server.

  2. The job engine must be switched on. This is required every time jobs are going to be executed. The server and job engine can be left on indefinitely, but this can be resource-intensive and costly. Jobs can alternatively be queued up while the server is switched off.

Both tasks are explained in this section of the Knowledge Base.

Curiosity also offer a number of ‘Quickstart’ automation frameworks that allow users to execute automated tests with very little setup. The available frameworks here include, Java, REST Assured and C#, with automated tests executing on a server maintained by Curiosity.


Test Execution Server - Software Requirements

Installing The Execution Server Video

The execution server must be hosted on a 64-bit Windows machine. There are three pieces of additional software that must be installed and licensed on the Windows machine that hosts the server:

  1. VIP is Curiosity's high-speed workflow automation engine, and is used to execute the automated tests.

  2. Chromedriver.exe. This is an open source tool for cross-browser test execution. It is included automatically in the set-up process below. You do not have to download it or perform any additional installation.

  3. Microsoft Excel must be installed and licensed on the machine that is used to set-up the execution server.

The job server must additionally be set up on the machine, and must be running for queued execution jobs to be performed.


Shared and Private Test Execution Servers

Two types of server that can be used to execute automated tests:

  1. A shared server. A shared execution server is available to everyone within a workspace. It only needs to be configured once, by one person in your domain. It is then available to everyone who shares that workspace.

  2. A private server. A private server is only available to the person who set it up.

The instructions in this section of the Knowledge Base set out how to check if there are any shared servers available for you to use. It then provides instructions on how to create a new private or shared server if needed.


How to Check for Available Execution Servers in Test Modeller

If using a shared server, only one member of your workspace needs to set-up the server. You should check if a server has already been set up for you to use before you configure a new server.

To check if there is an available server in Test Modeller, first log in to your domain. Next, click "Profile" in the sidebar menu, and select "Automation Servers". This will open the Server Settings page. Check the "Workspace Servers" panel to see if there are any servers already set up in your workspace.

If a server is available, you will be able to queue automated test jobs from within Test Modeller. 

To execute queued jobs, the job engine must additionally be switched on. Check the traffic light next to the name of the server.

  • If it is green, the job engine is switched on and active.

  • If it is amber, the job engine is switched on but inactive.

  • If it is red, the job engine is switched off.


How to Set Up or Upgrade The VIP Server for Test Modeller

Curiosity's process automation framework, VIP, runs the automation submitted to the server from Test Modeller, including automated test execution and test case generation.
This article and video provides instructions on setting up a server using VIP and exposing it to Test Modeller. In Test Modeller, it can then be accessed as either a Private or Public server.

Software Requirements

The Server can be set up on a local or cloud-based Windows 64-bit machine.  To set up the VIP Server, you will need the following Curiosity software installed on the Windows (64-bit) machine that will be used to host the Server. Please see the following Knowledge Base articles for guidance on their installation and licensing:

  1. VIP and its associated configuration folders.

  2. The VIP Server Controller and associated configuration folders.

Note: VIP and The VIP Server Controller have their own prerequisite software that must be fulfilled to set up the VIP Server. Please refer to the above guides to make sure that the prerequisites are fulfilled.
You will also need access to Test Modeller. Refer to this article for information on licensing and setting up Test Modeller.

Setting up or upgrading the VIP Server

The following video provides instructions on setting up the VIP Server. Use the video to complete the following steps on the Windows (64-bit) machine on which you will set up the Server:

  1. Install and integrate Test Modeller, VIP and The VIP Server Controller.

  2. Run The VIP Server Controller to commit the relevant automation workflows to memory.

  3. Use The VIP Server Controller to set up and run the Hopper and a REST Server.

  4. Set up a new private or shared server in Test Modeller.

  5. Run a test job to test that: available jobs are displayed in Modeller, that they can be submitted and run, that previous jobs are available for analysis, that the correct messages are displayed when jobs are run.

  6. Upgrade the VIP Server.

There are a three different servers shipped as standard with VIP and The VIP Server Controller:

  1. AUTO Server - primarily for running test automation scripts.

  2. Hopper - primarily for running advanced test data management jobs.

  3. REST Server - a back up server.

Choose to start whichever server is most relevant to the jobs being run on it.

How to Set up or Upgrade the VIP Server Video

Once you have set up your Server in Test Modeller, please refer to these Knowledge Base articles for instructions on submitting automation jobs.

TEST MODELLER AUTOMATED TEST EXECUTION