Sometimes, it may be difficult to understand why a test fails unexpectedly. In some cases, it may be caused by hardware performance drops, which may occur when you use ReadyAPI while working on extensive functional and load tests.
Since version 2.2, ReadyAPI Test and ReadyAPI Performance include performance monitors that help you determine when a problem occurs and eliminate its cause. When your functional or performance test reaches one of the limits specified in the rules, a warning or an error notification appears. You can see these notifications in the ReadyAPI log. They also appear in the UI, above the active panel of the test, or as dialogs.
| Note: | To learn how to disable notifications in the UI, see below. |
Once you solve a problem, no new notifications about it will appear.
The monitor checks the current system state every second during the test run.
Monitor rules
Depending on the application you are working with, ReadyAPI has a different set of rules for a notification to appear.
Functional tests
| Metric | Threshold Value | Time Amount | Notification Type | Description |
|---|---|---|---|---|
| XMX | 900 Mb | - | Error |
XMX – The memory allocation pool specified in the ReadyAPI settings file. If the XMX value specified in your vmoptions file is lower than the threshold value, the test will start, but an error notification will be shown during the test run. Increase the XMX parameter value and restart ReadyAPI to hide the error notification. To learn how to modify XMX, see Optimizing Memory Usage. |
| Used Memory | 80% | 10 seconds | Warning |
Used memory ––The percentage of the operating system memory available to ReadyAPI used by the product. For a notification to appear, the system must remain in certain state for the specified period of time. |
| Used Memory | 95% | 10 seconds | Error |
Used memory ––The percentage of the operating system memory available to ReadyAPI used by the product. For a notification to appear, the system must remain in certain state for the specified period of time. |
Performance tests
| Metric | Threshold Value | Time Amount | Notification Type | Description |
|---|---|---|---|---|
| XMX | 2 Gb | - | Error |
XMX – The memory allocation pool specified in the ReadyAPI settings file. If the XMX value specified in your vmoptions file is lower than the threshold value, the test will start, but an error notification will be shown during the test run. Increase the XMX parameter value and restart ReadyAPI to hide the error notification. To learn how to modify XMX, see Optimizing Memory Usage. |
| Used Memory | 80% | 10 seconds | Warning |
Used memory ––The percentage of the operating system memory available to ReadyAPI used by the product. For a notification to appear, the system must remain in certain state for the specified period of time. |
| Used Memory | 95% | 10 seconds | Error |
Used memory ––The percentage of the operating system memory available to ReadyAPI used by the product. For a notification to appear, the system must remain in certain state for the specified period of time. |
| CPU Usage | 90% | 10 seconds | Error |
CPU Usage – The percentage of the CPU time used by ReadyAPI. For a notification to appear, the system must remain in certain state for the specified period of time. |
 |
The amount of memory the operating system allocates for ReadyAPI also depends on the XMX value. That is, any problems that occur due to memory issues can possibly be resolved by specifying a greater value for XMX. See Optimizing Memory Usage. |
Solve performance issues
To improve the performance of your ReadyAPI tests, please consider the recommendations listed in Optimizing Memory Usage and Memory Management.
Disable performance monitor in UI
To disable the built-in performance monitor in the UI, set the Dtest.perf.monitor.output virtual machine option to log. You can do that by editing the vmoptions file. See Modifying JVM Settings for more information.