HTTP test generation preferences
Set Verification Points
To set verification points, go to...
Window | Preferences | Test | Performance Test Generation | HTTP Test Generation | Verification Points
Settings include...
- Automatically include verification point of
- Click to specify the types of verification points to be automatically included. If a check box for a verification point is selected, the code and edit controls for this type of verification point are generated in all tests. Verification points can also be enabled or disabled within specific tests.
- Accept sizes for primary request within
- If you are automatically generating response size verification points, click to specify the acceptable size range for primary requests. No error is reported if a response is within the specified percentage above or below the expected size.
By default, for primary requests, HTTP response size verification points use range matching.
Set Data Correlation preferences
For data correlation preference settings...
Window | Preferences | Test | Performance Test Generation | HTTP Test Generation | Data Correlation tab
Settings include...
- Automatically correlate host and port data
- By default, host and port data is correlated automatically.
If tests in a previous release have significant manual correlations, or you are using proxies, the migration of the replace host functionality feature is likely to fail during playback. In this situation, clear the check box. When you reopen tests, they will not have the automatic correlation feature in them.
- Optimize automatic data correlation for execution
Accuracy Default. Many references with an identical session ID value are created. The value of each session ID is substituted from the nearest previous reference. Efficiency Makes a test run faster by reducing the number of references created during automatic data correlation. For example, consider a test where a session ID, which is assigned when a user logs in, is included in each subsequent request in the test. With the Efficiency setting, all session IDs are substituted from a single previous reference.
The downside of this setting is that it can result in incorrect correlations.
For example, a request containing the string Joe Smith might be incorrectly correlated with a request containing the string Joe Brown.
- URL rewriting for execution
- How URLs are rewritten during test execution.
When correlating data, the test generator replaces part of a URL request string with a value that the server returned in response to a previous request.
Automatic Default. The test generator automatically determines when rewriting the entire URL during substitution will facilitate test execution. On Select to rewrite URLs in each instance of data correlation. This produces larger tests that take longer to run. Try this setting if tests fail unexpectedly. Off Select to manually correlate the instances where URL rewriting is needed. This setting might cause execution errors.
- Automatically correlate URL pathname if redirected by response code
- Whether URL path names are correlated if they are redirected by a selected response code. If a check box for a response code is selected, the test generator performs correlations for that response code.
To turn data correlation off entirely or to set whether names are automatically generated for data correlation references, click...
Window | Preferences | Test | Test Generation | HTTP Test Generation | Data Correlation
Set Protocol preferences
To access the preference settings for protocols, click...
Window | Preferences | Test | Performance Test Generation | HTTP Test Generation | Protocol tab
Settings include...
- Do not generate a new page if think time is less than
- Enter the shortest time, in milliseconds, that the generator uses as a delay to emulate user think time for an HTTP page. If tests contain fewer pages than expected, try a shorter interval.
- Generate a new page if delay between requests greater than
- Enter the longest delay, in milliseconds, that the generator allows between page requests. If this time is exceeded, a new page is generated. If tests contain more pages than expected, try a longer interval.
- Maximum request delay
- Enter the longest delay, in milliseconds, that the generator allows before truncating HTTP requests. The requests are truncated on the generated test. The recorded test still contains the original values, and you can get them back by generating a new test.
- Save only the first 4KB of responses larger than
- Enter the limit of response data, in KB, that the generator saves. If a response is larger than the specified limit, only the first 4 KB of data is saved.
- Data correlation
- When to generate data correlation constructs.
With the Automatic setting, the test generator creates the required constructs where needed. If the test does not contain the required constructs, change the setting to On, which will always perform data correlation. If tests do not require a specific construct, select Off, which has the additional benefit of improving performance on subsequent test generation.
- For Jazz Foundation Services, On and Automatic enable data correlation for Jazz applications that use REST storage or query APIs from Jazz Foundation Services. An example of such an application is Rational Requirements Composer. Although data correlation does not typically apply to browser-based Jazz web clients, it may be useful for other HTTP client-server applications that use REST services and the Atom Publishing Protocol for updating Web resources.
- For Jazz Web Applications, On and Automatic enable data correlation for Jazz Web applications that use the Jazz Foundation Web UI framework Examples of these Web applications are the Web interfaces for Rational Quality Manager and Rational Team Concert.
Data correlation may also be useful for other Web applications containing javascript that employs JSON for client-server data exchange. This is a common practice with DOJO- and AJAX-based applications.
Related reference