    |
|
You can create stress tests to determine how a Windows or Java application behaves under stressed conditions. You can add simulated stresses to test an application, such as low memory, low disk space, and read-only drives, or real stresses, such as disabled Windows networking.
You can add stresses to scripts during recording or manually add stress statements to existing scripts. The following example shows a stress test script.
Note: Stress statements cannot be used when recording new load tests or Helix ALM test cases, running load tests, or creating scripts from test cases.
Creating new stress test scripts
You can add stresses as you record new scripts. This is helpful if you want to enable stresses when the application starts or from a specific point in the script and use them throughout script playback.
Adding stresses to existing scripts
You can add stresses to existing scripts as you record additional steps.
You can also manually add stress statements to existing scripts. This is helpful if you want to enable and disable stresses at specific points during script playback.
Running stress test scripts
Run stress test scripts the same way you normally run scripts.
When playback completes, all simulated and real stresses are disabled, a run report is generated, and the tested application resumes normal operation. If email notifications are configured, the results are sent to specified recipients.
| |
|