- Installation and Upgrade Guide
Managing Your Organization
Users and Groups
Managing Picklist Values
Migrating Enterprise Tester from one server to another
Versioning & Version Control
Screen Field Configuration
Searching & TQL
Earlier Versions of this Documentation
The following sections outline the system requirements.
Supported Operating Systems
Enterprise Tester is supported on the following operating systems:
Windows Vista – SP2 Required
Windows 7 – SP1 Required
Windows Server 2008 - SP2 Required
Windows Server 2008 R2 - SP1 Required
Windows Server 2012
Windows Server 2012 R2
We recommend the following:
Minimum ( not recommended for Production environments)
30 Users and Above Server Deployments
2.0-3.0 GB depending on Usage
4.0-8.0GB depending on usage
2.4 Ghz x2
2.4 Ghz x2
Disk (operating system)
Configurations using less memory than this may run but performance will be severely degraded. Windows Vista/7/8 are only supported for trial use. We do not support these operating systems for a production platform.
The following browsers are compatible with Enterprise Tester:
- Internet Explorer 9
- Internet Explorer 10
- Internet Explorer 11
We recommend a minimum screen resolution of 1280x720 for best use of Enterprise Tester.
Enterprise Tester supports a number of different database servers which can be used with the product, these are:
- SQL Server 2008 R2 and above
- SQL Server Express 2008 R2 and above
- Oracle 10g / 11g
Please see the next section for database specific notes on setting the character set before you begin.
We recommend that the database is not installed on the same server as ET.
Database Specific Notes on Setting the Character Set
Enterprise Tester supports unicode strings in MySql databases, but you must ensure some steps are followed during initial setup.
Step 1 - Database Creation
When creating the database, you must specify UTF8 as the default character set and utf8 case insensitive as the default collation:
CREATE DATABASE `enterprisetester` CHARACTER SET utf8 COLLATE utf8_general_ci;
Step 2 - Configuring Character Set in Connection String
If your connection string to the MySql database is:
Then you must append the UTF8 character set declaration to end, like so:
If you have not set the UTF8 character set, there are ways to change the character set through a process of dumping out the database, performing a search/replace of all character set / collation declarations, then importing the modified database dump. Please consult your in-house MySql DBA for assistance.
Enterprise Tester supports unicode strings in Postgresql databases, but you must ensure some steps are followed during initial setup of the database. Before beginning, make sure you have a version of PostgreSQL that supports a column type of "uuid" (normally version 8.3 and later) as this is required by Enterprise Tester.
PostgreSql Databases must be created with a unicode encoding and we recommend using "UTF-8". If you use a non-unicode encoding such as WIN1252 Enterprise Tester will still work, but you may experience some issues when restoring baselines from other ET instances, importing data or when users save textual data that contains unicode characters.
For Postgresql to support unicode strings, you must create the database with the 'UTF8' encoding, like so:
Unlike MySql there is no need to change the connection string to accommodate UTF8 encoding. If you wish to learn more about setting the locale and collation for a PostgreSql database, please refer to the PostgreSql documentation:
The pre-requisites for installing Enterprise Tester are:
- IIS 7 and above
- The .Net Framework 4.5 installed.
- If you install IIS after the .Net Framework you will probably need to register ASP.Net for use with IIS
You may need to configure other components before Enterprise Tester will install or operate correctly.