Test Modeller Core (Linux) Installation
Search Knowledge Base by Keyword
1 – Copy files
A download link to a zip file with the exact version will be provided separately. Please contact support@curiosity.software for more information.
Download, transfer and unzip the provided ZIP file to the Linux server.
2 – Install Docker
Test Modeller API and web will be run as docker services.
Install Docker on a supported Linux distribution following the official instructions:
https://docs.docker.com/engine/installation/
3 – Install Docker-Compose
Docker Compose is a utility that simplifies the deployment and management of complete stacks. Follow the official instructions for installation:
https://docs.docker.com/compose/install/
4 – Configuring the Test Modeller Services
4.1 Basic configuration
Open the .env file in the in the unzipped folder for editing.
Change the following environment variables:
Variable | Default | Replace with |
HOST_ADDRESS | localhost | The machine name of the Linux host machine. This will be the URL that Test Modeller is accessed by in the browser. |
HOST_PROTOCOL | http:// | https:// if SSL is enabled. See this section for details. Default value is usually sufficient. |
HOST_PORT | 80 | 443 if protocol is https:// See this section for details. Alternatively, any other port if 80 is not available on the host machine. Default value is usually sufficient. |
LIC_OWNER | The license owner as provided. | |
LIC_KEY | The license key as provided | |
Storage on the host machine
The host machine will store the database data for Test Modeller, and so the directories that store it must be created and accessible. By default, the following two directories must be created on the host machine:
mkdir /data/postgres mkdir /data/neo4j |
If you wish to use other directories, you must edit the docker-compose.yml file and replace the following sections with your host machine directories:
services: postgres_db: … volumes: - /data/postgres:/var/lib/postgresql/data … neo4j_db: … volumes: - /data/neo4j/data:/data … |
4.2 Advanced configuration
For an advanced configuration you may need to edit further configurations with environment variables or changing the docker-compose.yml file, as advised during the installation procedure by curiosity. A list of the variables available for configuration is provided below.
TestModeller_Web
Variable | Default | Description |
HOST | localhost | Host name of the machine (IP address to be used to externally access server) |
HOST_ADDR | http://Localhost | Host address with protocol (http or https) |
API_ADDR | http://localhost:8080 | API location – default same machine on port 8080 |
TestModeller_API
Variable | Default | Description |
DATA_HOST | Postgres server location | |
DATA_USER | Postgres username | |
DATA_PASS | Postgres password | |
API_URL | Hostname of the API | |
GRAPH_HOST | Neo4j server location | |
GRAPH_PASSWORD | Neo4j password | |
GRAPH_USER | Neo4j Username | |
INSTALL_URL | Install URL of the webserver | |
SERVER_PORT | 8080 | Port to host the server |
EMAIL_AUTH* | True | Email auth |
EMAIL_HOST* | Email host | |
EMAIL_PASS* | Email pass | |
EMAIL_PORT* | Email port | |
EMAIL_TRANSPORT* | Email transport (smtp) | |
EMAIL_USER* | Email username | |
LIC_OWNER | Provided by Curiosity Software | License owner |
LIC_KEY | Provided by Curiosity Software | License key |
* Default email details are connected in the server for info@testmodeller.io
5 – Start the Test Modeller Services
Execute the run.sh script to load the containers and start up the services.
Note: you may need to run these commands using sudo.
sudo ./run.sh |
6 – Verify the deployment
Navigate to machine host and test you can sign in.
- Enter host URL (we installed ours on http://localhost)
This should bring up Test Modeller.
- Enter login credentials
The Default administrator user is:
Username: admin@testmodeller.io
Password: Admin01!
We recommend you can change this once logged in.
- Navigate to Models
You should see the default set of demo models installed.
-
-
-
- IEnumerable to Data Reader
- Data Table to List
- Nested String List to Data Table
- List to Data Table
- IEnumerable to List
- List to IEnumerable
- Remove from List
- Exists in List
- Value Exists in Dictionary
- Key Exists in Dictionary
- Remove from Dictionary
- Get from Dictionary
- Clear Dictionary
- Add to Dictionary
- Clear List
- Add to List
- Show all articles ( 1 ) Collapse Articles
-
-
-
-
- Explanation of Remaining Sheets in the Control Spreadsheet (for reference only)
- The ForeignKeys Sheet - Specifying which Foreign Keys to read from the Source Database
- The Tables Sheet: Defining Metadata that will be read from the Source Database
- The ProcessModel sheet – Toggling Subset Rules
- Refining the Control Spreadsheet
- Overview of the Advanced Control Spreadsheet
- Introduction
-
- Drop both Primary and Foreign Keys (The composite DROPKEYS Action)
- Validate Both Primary and Foreign Keys (The composite ValidateKeys Action)
- Add Both Primary and Foreign Keys (The Composite ADDKEYS action)
- Drop Tables
- Truncate Data
- Delete Orphans
- Drop Primary Keys
- Drop Foreign Keys
- Validate that Foreign Keys are Unique
- Validate that Primary Keys are Unique
- Add Foreign Keys
- Add Primary Keys
- Overview of Post-Subset Actions
-
-
- Use Event Hooks to call VIP Flows
- Different Methods for Connecting to Source Databases
- PreProcess Variables and Parameters
- Using SQL Functions to query Databases and Using the Queries in Data Generation Functions
- Summary of the Process to Configure the Test Data Configuration sheet
- How the PreProcessVariables Table is used in the Configuration sheet
- Sample Commerce Configuration Sheet Examples
- Adding Event Hooks in Configuration sheet for custom functionality
- How to Configure the Synthetic Test Data Configuration Control Sheet
-
-
-
-
-
- The UI Recorder
- Test Modeller – Maintenance
- Test Modeller Core (Linux) Optional – Postgres LDAP
- Test Modeller Core (Linux) Optional – SSL Certificate Installation
- Test Modeller Core (Linux) Optional – Active Directory
- Test Modeller Core (Linux) Installation
- Test Modeller: Software Pre-requisites
- Test Modeller : Installation components
- Test Modeller : System requirements (Windows, Linux)
-
-
-
-
-
-
- Common Problems
- Extend Test Modeller (Advanced)
- Edit Code Templates (Advanced)
- Import existing framework / custom page objects (Advanced)
- Execute Tests (Java)
- Generate Automation Code
- Build a Model (Java)
- Scan an Existing Web App
- Configuration (Java)
- Prerequisites (Selenium Java)
- Welcome Selenium (Java)
-
-
-
-
- Generate Optimised Test Cases and Data into Excel
- Implement Naming Conventions
- Page Object Generation
- Intelligent Page Objects
- Customising Page Objects
- Import Custom Code Snippets
- Rule-Based Test Generation
- Trigger Automation Execution from within Test Modeller
- Automation Configuration
- Test Data Automation for Gherkin Specifications
-
-