Worksoft Certify v12.1.2302 and Later Versions System Requirements
Before installing Worksoft Certify, ensure that your system meets the requirements listed below.
For information about Worksoft Certify Services system requirements, see Worksoft Certify Services v12.1.2302 and Later Versions System Requirements.
For Worksoft Certify Interfaces system requirements, see the Worksoft Certify Interfaces Requirements section.
Worksoft Certify Client System Requirements
|
Component |
Minimum Requirements |
Recommended Requirements |
|
Supported Operating System |
|
|
|
CPU |
2 processor cores (2.0 GHz or greater and 100 percent compatibles) |
2 processor cores (2.0 GHz or greater and 100 percent compatibles) |
|
RAM |
4 GB 8 GB - Using Worksoft Execution Suite with Certify |
4 GB 8 GB - Using Worksoft Execution Suite with Certify |
|
Storage |
1 GB |
2 GB |
|
Software |
|
|
Windows Azure
Worksoft Certify supports Windows® Azure® Infrastructure as a Service (IaaS) and Windows Azure Platform as a Service (PaaS).
Database Server Requirements
Worksoft Certify supports the following Standard edition database servers:
- Microsoft® SQL Server 2019
- Microsoft® SQL Server 2017
- Microsoft® SQL Server 2016 (SP1)
When you create a Certify database, you must estimate how large the database will become by figuring out usage. To help you determine your hardware requirements, Worksoft has provided the three following types of usage models:
- Light
- Medium
- Heavy
For database sizing questions, see Microsoft’s documentation on hardware sizing.
Light Usage Model
A Light Usage model is recommended for a small team that builds Certify processes and manually executes processes through the Certify user interface. This usage model is the typical starting point for most Worksoft customers. If you are starting with a larger team (more than 10 users), your usage may quickly outgrow the Light Usage model. In that case, please consider following the Medium Usage model recommendations.
The requirements for the Light Usage model are based on the following assumptions:
- Nightly execution has not been established yet because the test automation is still being built.
- Your SQL Server may host other software databases.
- Results maintenance is implemented with Certify SQL maintenance jobs once regular process execution has begun.
- Screenshots are only taken on a failed process step or a specific step.
Database Server Requirements
|
Component |
Requirements |
|
CPU |
2x 4-core processor |
|
Memory (RAM) |
16 GB |
|
Certify Database Free Disk Space |
50 GB |
|
Software |
Microsoft .NET Framework v4.5 (for running Certify database scripts) |
Medium Usage Model
A SQL Server Database Administrator is recommended for professional planning and maintenance for a Medium Usage model.
A Medium Usage model is recommended for a medium to large team that builds Certify processes and manually executes processes through the Certify user interface. If you are just starting with Certify and know that you will have 10 or more concurrent users creating Certify test processes, you should consider implementing this usage model instead of the Light Usage model to account for future growth.
Please note that the number of Certify users actually creating processes is not the primary reason for choosing to implement this usage model. The primary reason for choosing this model is the number of processes and executions you expect to be running on a daily basis.
The requirements for the Medium Usage model are based on the following assumptions:
- Certify process execution is done daily across 50 virtual machines, and 700 transactional Certify processes are executed continuously for 8 hours.
- Your SQL Server may host other software databases. Worksoft recommends that no other Worksoft software is installed on the SQL Server.
- Results maintenance is implemented with Certify SQL maintenance job to archive and delete results.
- Screenshots are only taken on a failed process step or a specific step.
Database Server Requirements
|
Component |
Requirements |
|
CPU |
2x 4-core processor |
|
Memory (RAM) |
16 GB |
|
Certify Database Free Disk Space |
100 GB |
|
Software |
Microsoft .NET Framework v4.5 (for running Certify database scripts) |
Heavy Usage Model
A SQL Server Database Administrator is required for professional planning and maintenance for a Heavy Usage model.
Similar to the Medium Usage model, a Heavy Usage model is recommended for a medium to large team that builds Certify processes, manually executes processes through the Certify user interface, and executes a large number of Certify processes daily. If you are just starting with Certify and know that you will have 10 or more concurrent users creating test processes with Certify and executing a large number of processes nightly, you should consider implementing this usage model instead of the Medium or Light Usage models to account for future growth.
Please note that the number of Certify users actually creating processes is not the primary reason for choosing to implement this usage model. The primary reason for choosing this model is the number of processes and executions you expect to be running on a daily basis.
The requirements for the Heavy Usage model are based on the following assumptions:
- Certify process execution is done daily across 120+ virtual machines, and 1,500 top-level Certify processes are executed continuously for 8 hours.
- Your SQL Server is dedicated to the Certify database. Worksoft recommends that no other Worksoft software is installed on the SQL Server.
- Results maintenance is implemented with Certify SQL maintenance job to archive and delete results.
- Screenshots are only taken on a failed process step or a specific step.
Database Server Requirements
|
Component |
Requirements |
|
CPU |
2x 8-core processor |
|
Memory (RAM) |
32 GB |
|
Certify Database Free Disk Space |
300 GB Dedicated LUNs for data, log, tempdb, and backups. Free space is monitored, and the LUNs are extended on demand when a low disk space threshold is crossed. |
|
Software |
Microsoft .NET Framework v4.5 (for running Certify database scripts) |
SQL Server Collation Requirement
Worksoft Certify requires the following for SQL Server Collation:
-
Character set to be ASCII equivalent.
Example: Latin1
- Code Page 1252 (CP1).
Worksoft Certify supports both case sensitive (CS) and case insensitive (CI), and it is accent sensitive (AS).
Example : SQL_Latin1_General_CP1_CI_AS
SQL Server Mixed Authentication Mode
When setting up a Certify Database, it is recommended that you select Mixed Authentication Mode during your SQL Server configuration. Mixed Mode enables both Windows and SQL Server authentication.
Worksoft recommends Mixed Mode for the following benefits:
- Only one database logon user is necessary
- User ID and password are encrypted in the Certify configuration
Enabling SQL Query Optimizer (Trace Flag 4199)
For Certify to have acceptable performance in SQL Server, Trace Flag 4199 must be implemented at the SQL Server service level. Without this flag enabled, the SQL Server Query Optimizer will be disabled and Certify will respond very slowly.
Instructions for setting up this Trace flag in SQL Server are available in several Web sites.
After this trace flag is enabled, the average response times for queries in Certify are reduced. For example when changing between Process folders in Certify without Query Optimizer enabled, it could take up to 35 seconds. With the Query Optimizer enabled, it takes only a few seconds.
- Note: You do not need to set Trace Flag 4199 manually if you are using SQL Server 2016 or a later version with Compatibility Level set to SQL Server 2016 (130).
Network Requirements
Security
Confirm that TLS 1.0 or TLS 1.2 is enabled.
Latency
To use Certify in Classic mode, the required network latency between the Certify Windows client and database is under 30 milliseconds.
To use Certify in Automator's mode, the required network latency between the Certify API Server and the database is under 30 milliseconds, and the required network latency between the Certify client and the Certify API Server is under 300 milliseconds.
License Server Requirements
With Worksoft Certify v12 and later releases, you will use Worksoft Portal or Worksoft Management Studio for licensing. Worksoft Portal is replacing Management Studio as the administration tool for Worksoft products.
If you are a new customer, Worksoft Customer Support will provide you with Worksoft licenses.
For Worksoft Portal system requirements and installation information, see Worksoft Portal Help.
For Worksoft Management Studio system requirements and installation information, see Worksoft Management Studio Help.
Worksoft Certify Interfaces Requirements
Listed in the table are the requirements for each Worksoft Certify interface extension.
|
Interface |
Requirements |
|
Applitools |
Applitools If application running on a Mac®, you need the following:
|
|
Certify Interface for Microsoft Office® |
|
|
Web |
The screen Dots Per Inch (DPI) must be set to 96. If the DPI is set to something else (i.e. 120), selects/clicks will not occur in the right locations and the process steps will fail during test execution.
Worksoft Certify automatically installs the Worksoft Automation Extension to the Edge, Firefox, and Chrome browsers. You need to verify that the extension is enabled. For more information on how to verify that the extension is enabled, click here. For customers using Microsoft Internet Explorer legacy browser, click
 here.
The Web interface supports both the Internet Explorer v11 browser, as well as the Internet Explorer control. Internet Explorer v11 is the legacy browser integrated with the Windows operating systems, and it was permanently replaced by the Microsoft Edge browser. The Internet Explorer control allows applications to embed web content within one or more screens. These embedded controls are used to implement SAP HTML controls in older versions of the SAP GUI. Also, these controls are used to implement the Edge browser’s Internet Explorer Compatibility feature. Both the Internet Explorer v11 browser and control are capable of creating a document using the latest engine or one of the legacy Internet Explorer engines. By default, a page loads using the Internet Explorer v11 engine, but if a web page or site include special information, it can let tell the engine to use one of the older engine modes for compatibility. The Web interface supports documents rendered in modes v9, v10 and v11. It is not possible to determine what document mode is being used. If the Web interface does not appear to be working against an application running in Internet Explorer, you can use the Internet Explorer Developer Tools to identify the document mode of the web page. This tool is located in the upper right corner of the Tools window and it appears as a number. In addition, Certify v12.1.2206 and later versions provide a DocumentMode property on the Browser, IFrame, and Frame nodes in the Certify Web Learn tree. |
|
Java |
Java® Runtime Environment (JRE) 6 (v1.6) , 7 (v1.7), 8 (v1.8), and 11 (supports OpenJDK and Oracle Java). Both 32-bit and 64-bit JREs are supported when available. For each JRE used by the application under test, you must run the Worksoft JAR Installer. SWT applications not supported. |
|
Mac |
Headless Operation A headless operation is when a monitor is not attached, such as a virtual machine that connects with remote software (Apple Remote Desktop, VNC, etc.) to a server instance. When automating applications on a Mac system that is headless, screen captures may not function correctly. In such cases, an HDMI emulator device, such as the CompuLab Display Emulator (fit-headless) or an equivalent emulator, can be used to enable screen capture functionality. |
|
Mainframe |
The following emulators are supported for use with the Mainframe interface:
Only 32-bit versions of Windows desktop emulators are supported. Java emulators and 64-bit versions of emulators are not supported. For information on how to set up the emulators, see the Worksoft Certify Installation Guide. |
|
Mainframe LT |
The following emulators are supported for use with the Mainframe LT interface:
Only 32-bit versions of Windows desktop emulators are supported. Java emulators and 64-bit versions of emulators are not supported. To create a step with LiveTouch, you need to have Aviva for Desktops™ emulator (32-bit only). For information on how to set up the emulators, see the Worksoft Certify Installation Guide. |
|
Mobile |
Requires one of the following:
|
|
NetUI |
Used for applications written in Microsoft .NET Framework v4 and later versions |
|
Oracle® Forms |
Java® Runtime Environment (JRE) v1.6 (6.0), v1.7 (7.0), and v1.8 (8.0) For each JRE used by the application under test, you must run the Worksoft JAR Installer. |
|
PDF Forms |
Adobe® Acrobat® v8.0 and later versions for standard and professional versions Adobe® Reader® is not supported. |
|
SAP |
SAP GUI for Windows v7.5, v7.6, and v7.7 with the latest patch SAP GUI for Windows v7.5 patch 4 is required when using the Fiori theme and connecting with SAP HANA SAP® GUI for Windows® v7.1, v7.2, v7.3, or v7.4 with the latest patch The SAP interface also supports SAP Netweaver® Business Client v3.5 and v5.0. You are able to install SAP Netweaver Business Client v5.0 with SAP GUI v7.4. |
|
Silverlight® |
Uses Microsoft® UI Automation and supports applications that provide Win32 or Accessibility hooks. |
|
Certify-SmartBear SOAPUI |
Requires one of the following:
|
|
UNIX |
Reflection® Desktop (formerly Attachmate® Reflection®) for UNIX and OpenVMS 2011 R3 You must install support for Reflection Desktop .NET API because it is not included by default. To install this feature, right-click Application Programmer Interface in the Reflection Desktop Feature Selection tab and select Feature will be installed on the local hard drive. |