This appendix contains an example use-case definition taken from a real performance testing project. Figure A-1 demonstrates the sort of detail you should provide for each use case to be included in your performance test. The example is based on a spreadsheet template that I have developed to capture use case information.
Ideally, you should create a similar template entry for each use case that will be part of your performance testing engagement.
Please see the following for an explanation of the template contents:
Each use case should have a meaningful name such as “Bill Payment” in the example.
This is a calculated value based on the number of web page view per use case step where this is relevant.
The order that this step occurs in the use case.
There are three options available:
Whether this use case step is to occur only once at the start of a performance test.
Whether this use case step is to be iterated during performance test execution.
Whether this use case step is to be executed only once at the end of a performance test.
A description of the user action required for this use case step (e.g., step 1 requires the user to “Enter online banking number, an Internet password, and then click Continue”).
A label ...