You can set performance requirements on protocol-specific test elements, on schedule elements, on data created by custom code, and on collected resource usage data. You define a performance requirement as standard or supplemental. A standard performance requirement is a requirement that you determine is significant enough to cause the entire run to be declared a failure if it fails. A supplemental performance requirement, although important, is not significant enough to cause the run to fail. For example, a supplemental performance requirement might be a request from development to validate a very specific data item provided by WebSphere® PMI monitoring.
To define a performance requirement for the elements in a test:
Option | Description |
---|---|
Name | You can change the name of a performance requirement to improve readability. However, changing a requirement name causes a mismatch between the Performance Requirements report, which uses the changed name, and the other reports, which use the default name. Therefore, when you change a requirement name, be sure to keep track of the original name. |
Operator | Select an operator. |
Value | Type a value. |
Standard | Select to make the requirement standard. A standard requirement can cause a test to have a verdict of fail. Clear to make the requirement supplemental. In general, supplemental requirements are used for requirements that are tracked internally. A supplemental requirement cannot cause a run to fail, and supplemental results are restricted to two pages of the Performance Requirements report. |
For example, assume that you select every page in a test and define this requirement: Average response time for page [ms] [For Run] must be less than 5 seconds. This means that if one page in the test has a response time of 6 seconds, the requirement on that page fails. The other pages, which have a response time of less than 5 seconds, pass.
Assume that you open a schedule and define this requirement: Average response time for all pages [ms] [For Run] must be less than 5 seconds. This measures the average response time for all of the pages. One page can have a response time of 30 seconds, but if enough pages have a response time low enough to counter the negative effect of that one page, the requirement passes.
For information on defining requirements in schedules, see Defining performance requirements in schedules.