This topic describes system requirements for ReadyAPI. For information about VirtServer requirements or TestEngine requirements, see the topics in the appropriate sections.
Supported operating systems
-
Windows 8.1, Windows 10 and Windows 11 (64-bit).
-
Windows Server 2012 - 2019.
-
macOS 10.13 (High Sierra) - 12 (Monterey).
-
64-bit Oracle Linux 6 - 8.
-
64-bit Red Hat Enterprise Linux 6 - 8.
-
64-bit Suse Linux Enterprise Server 12 - 15.
-
Ubuntu Linux 20.04.
Note: |
ReadyAPI is updated to support Adoptium JDK 17.0.12 in ReadyAPI 3.57.0. 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 with your Virtual Machines and Docker instances. |
Recommended system requirements
-
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.
Minimal system requirements
-
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 requirements
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.
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.
Groovy debugging requirements
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>\lib folder. You can get this file from the <JDK installation folder>\lib folder.
-
Place the attach.dll file in the <ReadyAPI installation folder>\bin folder. You can get this file from the <JDK installation folder>\jre\bin folder.
API Import times - Reference Testing
The following table shows some sample API import times based on SmartBear tests, using this setup:
-
OS: Window
-
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 | |
Aysnc API | 1.04 MB | 1768 | 38287 | 1768 | 17s |
Note: | This data is only for reference because many factors affect the import API file time in ReadyAPI such as file size, the complexity of each API (ex: the body of the API is heavy or light, #parameter, #queryParam, etc...), the number of parameters, and the number of references. |