Skip to main content

System Requirements

Operating System

Microsoft® Windows 10
Microsoft® Windows 11


Monitor Resolution

Recommended: 1080p (1920 x 1080)
On some HiDPI displays, Cycle may have difficulty positioning the cursor consistently, this is a hardware issue. More info


Local System Resources

Use CaseCPUDisk SpaceMemory (RAM)
Regression TestingMinimum: 2.0 Ghz - Quad Core
Recommended: 2.5 Ghz - Quad Core
Minimum: 2 GB
Recommended: 10GB*
Minimum: 8 GB
Recommended: 16GB
Performance Testing2.5 Ghz - 8 Logical Processors**SSD16GB

Ensuring as few other applications are open as possible and occasionally restarting Cycle will improve user experience.

*Additional space may be needed as test artifacts such as reports and images are produced.
**For devices that support hyper-threading or simultaneous multithreading (SMT), multiply the number of cores by threads to identify the number of logical processors. Otherwise, the number of cores is the same as the logical processors.


Performance Testing support

Performance Testing is supported for the following:

  • Browsers: Chrome, Edge
  • Technologies: Web, Terminal, API, Database

Cycle can support 10 concurrent Chrome or Edge sessions on a single device or 30 concurrent terminal sessions on a single device.

Reach out to your Technical Account Manager for any technologies not listed, if you would like to explore Edge IE Mode/Windows Native App performance testing, or if you are facing limitations scaling API performance testing.


Cloud Infrasructure for Performance Testing

CloudSizingvCPUsRAMStorage Type
AzureStandard_F8_v3816GBSSD
GCPc2-standard-8832GBSSD
AWSt3.2xlarge832GBSSD

VMs should be non-burstable to avoid throttling resources in resource instensive activities. If cost is an issue, consider dynamically spinning up agents on spot VMs, with some additional agents for expected loss in cloud infrastructure.

Java Heap Size should be set to 8GB for performance testing. This can be configured by specifying -Xmx8G in the Cycle Server Tuning Parameters. When running Cycle CLI, you must set them in an OS environment variable named JETVMPROP.

Image Capture should be disabled to optimize Cycle performance during a performance test. This setting can be found under Execution Settings as "Save failure screenshots."


Additional Requirements

Web Application Testing

Latest: Chromedriver | Internet Explorer Driver | Microsoft Edge Driver
More info

Legacy applications may have interfaces that can not be scaled for IE Mode performance testing


Windows Native Application Testing

Microsoft® Windows 10 or higher
Microsoft® Windows Server® 2016 or higher
Windows Developer Mode enabled
Windows Accessibility Insights (for element identification)
More info

Limited to one worker per VM for performance testing


Java App Testing

Microsoft® Windows 10 or higher
Microsoft® Windows Server® 2016 or higher
Java 8
System Environment Variables for Java Home and Marathon driver (more info)


SAP ECC Testing (BETA)

Deployment of Jacob DLL into the Cycle Java bin (more info)
System Environment Variables for Java Home and Jacob DLL (more info)