System Requirements
This topic outlines the system requirements for ReadyAPI. For information about VirtServer requirements or TestEngine requirements, see the topics in the appropriate sections.
Microsoft Windows
Windows 10 22H2
Windows 11 22H2 or later
Windows Server 2016 or later
Apple
macOS 15 Sequoia or later
Linux
Oracle Linux 8 or later
Red Hat Enterprise Linux (RHEL) 8 or later
SUSE Linux Enterprise Server (SLES) 15 or later
Ubuntu Linux 20.04 or later
Note
ReadyAPI is updated to support Adoptium JDK 21.0.9+10 in ReadyAPI 3.64.0. The Installers automatically install the appropriate Java version, and we recommend using the Java version bundled with the product. Support for this version will also be required for your Virtual Machines and Docker instances.
Some Linux distributions may not have all the required packages installed by default. If compatibility issues arise, users should review the installation logs and manually install any missing libraries. On RHEL 9, the freetype library is a prerequisite for the installation of ReadyAPI or VirtServer. RHEL 9 and VirtServer do not include the library by default. Run sudo dnf install freetype to install the latest version. Ensure you have sudo privileges to complete the installation.
Intel Core i5 or i7 (the 3rd generation or later) or an equivalent AMD processor.
16 GB of RAM or more. At least 1 GB of free RAM is required to start ReadyAPI.
600 MB of free disk space for installation.
64-bit operating system.
1920 × 1080 display.
Intel Core i3, i5, or i7 (the 3rd generation or later).
8 GB of RAM or more. At least 1 GB of free RAM is required to start ReadyAPI.
600 MB of free disk space for installation.
1280 × 1024 display (widescreen monitors are recommended).
ReadyAPI Performance runs a large number of tests in parallel. To make sure your load tests work as expected, you need a more powerful computer than for other test types:
Intel Core i5 or i7 (the 3rd generation or later) with at least 4 threads.
8 GB of RAM or more.
An SSD with at least 1 GB of free disk space.
Important
The requirements above are for small- and medium-scale load tests. For information about large-scale tests, see System Requirements for Large-Scale Load Tests.
Additionally, since the logs of long-running tests may exceed 1 GB, we recommend having at least 8 GB of RAM on the machine where you try to open them.
To run Groovy debugging, ReadyAPI uses the tools.jar and attach.dll files from the Java JDK. These files are included only in the installation package and in the win-32 archive. This is done to avoid possible conflicts with the JRE installed on your computer.
To enable debugging for binary packages:
Place the tools.jar file in the
<ReadyAPI installation folder>\libfolder. You can get this file from the<JDK installation folder>\libfolder.Place the attach.dll file in the
<ReadyAPI installation folder>\binfolder. You can get this file from the<JDK installation folder>\jre\binfolder.
ReadyAPI applies strict security controls to block connections that rely on weak TLS ciphers. Any client endpoint that uses these ciphers is rejected to ensure secure communication and compliance with modern cryptographic standards.
This enforcement affects scenarios such as SLM On-Premise when it is configured to use HTTP or when the server uses outdated cipher configurations.
If you need to temporarily allow weak ciphers, for example, while updating a legacy server, you can override this behavior with the following JVM parameter:
-DallowWeakCiphers=<value>
Set the value to true to allow weak ciphers. For details, see Java Virtual Machine Parameters.
Examples of blocked ciphers:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHATLS_ECDHE_RSA_WITH_AES_256_CBC_SHATLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHATLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_DHE_RSA_WITH_AES_256_CBC_SHATLS_DHE_DSS_WITH_AES_256_CBC_SHATLS_DHE_RSA_WITH_AES_128_CBC_SHATLS_DHE_DSS_WITH_AES_128_CBC_SHATLS_DHE_DSS_WITH_AES_256_GCM_SHA384TLS_DHE_DSS_WITH_AES_128_GCM_SHA256TLS_DHE_DSS_WITH_AES_256_CBC_SHA256TLS_DHE_DSS_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_CBC_SHATLS_RSA_WITH_AES_128_CBC_SHA
The following table shows some sample API import times based on SmartBear tests, using this setup:
OS: Windows
Intel Core i5 3337U 1.8GHz
16 GB of RAM bus 1600 MHz
Disk 256 GB SSD
64-bit operating system
1366 × 768 display
API Type | Size | #API | #Line | #Resource | Import File |
|---|---|---|---|---|---|
REST | 600 KB | 3124 | 37683 | 785 | 17s |
SOAP | 2.2 MB | 3073 | 39988 | 1158 | 17s |
GraphQL | 132 KB | 2043 | 2780 | 2 | 15s |
1.3 MB | 1128 | 35885 | 2 | 1h45m | |
Async API | 1.04 MB | 1768 | 38287 | 1768 | 17s |
Note
This information serves as a general reference. Import time in ReadyAPI varies based on several factors, including the size of the API file, the complexity of each API (for example, large or detailed request bodies, many parameters or query parameters), and the number of parameters and references involved.