Installation requires two machines to be provisioned:
1. A Linux based machine for hosting Docker with the Test Modeller Databases, API, and Web front end.
2. A Windows based machine for hosting the VIP server (data provisioning).

System requirements: Windows

  • Windows Server 2013 Enterprise / 10 Pro minimum – 64-bit edition

  • 64bit Processor (i3 minimum – Intel Core i7 recommended)

  • Microsoft .Net 4.8 Framework• Minimum 8GB Ram (16GB Recommended)

  • Minimum 20GB Hard Drive space

  • Port 8080 outbound communication.

Additional ports may be required if utilising additional VIP servers. These should be placed on ports (8081 – 8085). Port 443 is also used if connecting to any SSL based services (e.g. Slack).

Note: If hosting databases separately, the respected database ports will also need to be open (7474. 5432).It is recommended the server is profiled to monitor the performance as capacity increases.

Software Requirements for Test Modeller

Windows Machine:

  • Microsoft Excel (64-bit)

  • .Net framework 4.8 Runtime

User machines:

  • Google Chrome (If performing functional UI testing using the UI Recorder and scanner)

Installation Components for Test Modeller

  • Test Modeller (Linux) – The core modelling component, server via docker containers. Consists of an API (hosted via TomCat container) and web front end (via apache container) –

  • VIP – A workflow engine for automating business processes. Used by Test Modeller to automate DevOps pipelines. Curiosity Software Products.

  • VIP Server – A server instance which connects Test Modeller to VIP to perform long-running tasks within Test Modeller (path generation, exports, automation generation)

  • The UI Recorder – A Chrome extension that is installed if performing functional web UI testing. The extension records test activity and scans page elements.

Test Modeller Architecture

The below diagram illustrates the full Test Modeller, Test Data Automation, and VIP architecture.

The below docker container dependency map illustrates the many dependencies between the docker containers that make up the installation.