Stressless Load Testing

All About Performance Testing & Tools for Web, Mobile and API

What's new in v2.5, Part 2 - Test Case features (Enterprise and Pro)

1. Session Verification Tree. The results of test verification in the Verify Test Case sections are now displayed in the Session Verification Tree. From the toolbar, the user can select 3 Views: All URLs, Errors, or Warnings. Each item on the tree allows easy toggle between the recorded and replayed sessions to quickly compare their content using any Fiddler inspector.

 

2. Session comparison inspector. Fiddler provides an option to compare two selected sessions using Windiff or other text comparison utility. However, many StresStimulus users do not have Windiff or similar utility installed or configured with Fiddler. Besides that, Windiff provides poor text comparison functionality because it only highlights lines, but not characters that are different in the two sessions.

A new Session Comparison Inspector removes these limitations. It has features available in commercial text-comparison tool and can be invoked from the Verify Tree or from the Fiddler grid. The pop-up window highlights specific differences in the recorded and replayed parameters that simplifies troubleshooting test errors.

 

3. Extractor Validation Tree. Test verification now allows to easily check whether extractors are configured and used correctly. The Extractor Validation Tree displays the value of every extractor that was validated. It also displays an error if the extractor cannot be validated or warning that the extractor is not used by any parameter.

 

4. Extractor Tree. Extractors are now displayed in a separate tree linked to a property grid, allowing easy instructors editing. The tree shows all parameters where the extractor is used. The user can easily identify extractors that are not used in the test case. Like all specialty trees, the Extractor Tree allows to easily navigate to extractors and parameters by double-clicking them.

 

5. Auto-Cloning parameterization rules. Multiple similar parameterization rules can now be created with a single click. To clone a selected parameterization rule to all parameters with the same name in the subsequent requests, simply click the clone button on the toolbar. For example, this feature can be used to feed-in a dynamic session ID to all subsequent requests. In previous versions it is required to create multiple each individual parameterization rules manually. In 2.5 the same can be performed with a single click.

 

6. Renaming User Actions in the Recorder. The StresStimulus recorder captures page titles from the HTML and displays them in the Test Case Tree. However, sometimes it is helpful to identify pages differently, depending on the user actions. Now, the recorder allows renaming the page right after the user clicks, when it is easy to remember what user action was.

Here's an example of how this feature can be used: In the Recorder, highlight the last captured request before executing the user action that you want to rename. After executing the user action, rename the request next to the highlighted request. After the recording is complete, the page names will be transferred to the Test Case Tree.

 

 

7. Easy renaming Dataset fields. A Rename button is added in the datastore edit window for easily renaming any Dataset field.

 

8. Remove the limitation of using Iterations Per User. In previous versions, it was not possible to combine the "Number of Iterations Per User" option with the Step Load pattern. In 2.5 this limitation is removed.

 

 

9. Better control over starting tests from command line. Previously, we recommended to use the Fiddler utility, ExecAction.exe, for scheduling load tests at periodic intervals, as was described in item 13 of this post http://www.stresstimulus.com/blog/post/what-s-new-in-v1-7

Now StresStimulus has its own command line utility called LaunchFiddler.exe that removes the following two limitations:

  1. It provides more reliable communication with Fiddler, as in some cases ExecAction cannot communicate with Fiddler.
  2. LaunchFiddler, unlike ExecAction, can communicate with Fiddler even when it is closed. In this case it will launch Fiddler first.

LaunchFiddler should be used exactly the same as, and instead of ExecAction.

 

10. V2.5 includes substantial internal re-architecting as a first step of implementing Standalone StresStimulus Roadmap. In spite of that, the load engine and analytical module remain virtually unchanged. Because of this, the high reliability and accuracy of v.2.5 is secured.

To navigate to other parts of the v2.5 release notes, click the links below:

V2.5 beta is available for download here.

blog comments powered by Disqus