Load Tester™ New Features
New in 3.3 Release
| New Feature | Description |
|---|---|
| Advanced Configuration | Web Performance Analyzer™ extensively analyzes your test case and automatically performs the routine configurations required for most test cases, saving many hours of labor on each test case. For those test cases that require additional manual configuration, this task has previously required a high level of knowledge of the product and/or help from our support personnel. For help the user understand the new functionality there is a new tutorial that can help even the novice load-testers understand and configure complex test cases. Many of the new test case configuration options for this release are addresses specifically in this tutorial. |
| User-defined Field-detection Rules | The ASM wizard uses an extensive set of default rules for finding and configuring client-state variables in web pages for accurate test case simulation. With the addition of User-defined Field-detection rules, you can provide the ASM wizard with additional rules for locating and configuring these fields. Previously, this required the user to manually configure extractors and modifiers on each instance of a field. By specifying a detection rule, ASM can perform this work automatically, saving many hours of work for each test case. |
| ASM Field-ignore Preferences | The run-time performance of Load Tester can be optimized by instructing the ASM wizard to ignore fields that will never change for a particular test case. Previously, these fields must be selected each time the ASM wizard was executed. Now these fields may be specified in the Ignored Fields preference page and the ASM wizard will automatically ignore them each time. |
| Dynamically-named Fields support | Some application frameworks use groups of fields that are numbered based on the value of another field. In earlier releases, handling these cases was impossible without assistance from our support personnel. Dynamically-named field schemes may now be configured by novice users with relative ease, allowing you to get your tests up and running quickly. |
| Validation Rules | Building a good test case sometimes requires configuration of validators on every page in a test case This can be an arduous and repetitive task consuming valuable testing hours. Validation rules may now be specified to automatically apply validators, as needed, to one or many pages in a test case This is especially useful when checking for common error messages that are generated automatically by application frameworks. |
| Domain and URL Blocking | Many test cases can be polluted with URL's that are not useful for load-testing purposes. These include URL's fetched automatically by toolbar plugins (Google, Yahoo, etc) and by advertising or usage-tracking URL's on external sites. Corporate portal pages may also references to many off-site URL's that should not be included in a load test. Previously, these transactions required manual deletion to get the desired load test results. Domains and individual URL's may now be blocked during the recording phase, automatically excluding them from the test case |
| Streaming Media Support | Some test cases with large resources, such as streaming media, resulted in metrics on a recorded test cases that was not as accurate as possible. Users may now turn on streaming-media support before recording these test cases to generate more accurate measurements and a more realistic test case simulation. |
| Fixed-repeat Load Tests | Previous versions only allowed configuration of a load test with a fixed duration. A load test may now be configured to end after all test cases have completed a fixed number of iterations. |
| IP Aliasing Configuration | Load Tester has supported the use of multiple IP addresses for generating load to your server for many versions. However, using this feature required manually adding a line for each IP address to a text file on each engine. This task may now be accomplished with a few clicks from within the GUI. |
| Misc. Improvements |
|
