System Requirements and Prerequisites
To install and use Squash TM, please see the minimum and recommended requirements below:
|Minimum (for trial)||Single-core||1 GB dedicated||1 GB||Linux, Windows, Mac||Firefox, Chrome|
|Recommended||Bi-core||2 GB dedicated||5 GB||Linux||Firefox or Chrome|
The hard drive disk (HDD) will be used to store logs and the database if it is on the same server.
The app itself and its files weigh 130 MB. You need at least 200 MB of free disk space if you want to store Squash TM and its logs. But if you want to also store Java and Squash TM database on the same server, you need at least a minimum of 1 GB of free disk space.
These elements are only given as an indication. They cannot replace a complete study that takes into account the target context.
Table of middleware versions compatible with Squash TM:
|Minimum production environment||Recommended|
|Operating system||Any Linux or Windows system||Debian 11, Centos 7|
|Java||JVM version 11 LTS||JVM version 11|
|Database||Postgresql 11+, Mariadb 10.6||Potgresql 13, Mariadb 10.6|
With Squash TM 5.0, MariaDB 10.5 and previous versions are no longer supported.
As a reminder, Squash TM is not compatible with MySQL since version 4.0.0.
More details on the middlewares.
- Operating system: Any system that is able to run a JVM.
- App implementation/daemon: For Linux compatible systems, a systemd service file is provided. For Windows, a script creating the service is provided.
Virtual machine: A JVM Hotspot is enough to execute Squash TM. Version 11 is recommended. Squash TM works very well with a JDK.
Henix mainly uses the JVM Hotspot distributed by Oracle.
Application server: No application server is required, as Squash TM embeds its own Apache Tomcat. If you wish to deploy Squash TM using your own application server, you can. However, Henix does not recommend this method.
- Henix recommends that you use PostgreSQL 13. You need at least PostreSQL 11 for it to be compatible with Squash TM.
- Henix also recommends that you use Mariadb 10.6. You need at least MariaDB 10.2 for it to be compatible with Squash TM.
Squash TM is delivered with an embedded base (H2) that can be used for evaluation purposes. We do not recommend you to use it in a production context.
Please visit the page Install database to learn how to use another database than H2.
- Other software recommendations:
- Mantis 2.x+ or Jira 8.4+
- Apache HTTPD (frontal web)'s latest version
For small volumes and a limited number of users (less than 50), Henix recommends a "three-level" architecture. In other words, on a virtual machine, you install these three services:
- Frontal Web
To deploy Squash TM within a shared infrastructure, it is possible to have the three services on three different systems and to interconnect them through the network.
The reverse proxy is optional, but we recommend you to use it for two reasons: first, to separate the access logs from the application logs; and second, to entrust the TLS encryption to another process/service than Squash TM, even if the app's embedded Tomcat server is able to do it.
We highly recommend that no matter the volumes, to have both Squash TM and the database on the same server so as not to slow down performance with additional processes.
Recommendations for Squash AUTOM use
There are no prerequisites to install and use Squash TM with the Squash AUTOM orchestrator:
- To use the Squash AUTOM orchestrator with Squash TM, you just have to install the required plugins
To learn more about Autom plugins, please visit the page Squash TM Plugins
- When it comes to sizing the database, it will depend on the quantity and frequency of automated tests results transmitted to Squash TM. Squash TM has a feature to help you regulate the volume of automated executions: Automated suites cleaning
- The orchestrator is packaged as a Docker image but exchanges with Squash TM are done via REST calls, so you do not need to also install Squash TM as a Docker.