Stressless Load Testing

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

V3.0 update #2

Update #2 released today includes new features and enhancements in the following categories:

UI improvements

1. Workflow of the load testing process is reflected in the UI. Navigation Tree is renamed to Workflow Tree and is adjusted to reflect 4 main steps in the load testing process:

  1. Build Test Case
  2. Configure Test
  3. Run Test (new node)
  4. Analyze Results

2. Test case properties are added to the Page Settings node and it is renamed to Test Case Settings.

3. The Configure Monitoring node is added to the Workflow Tree.


Built test case

4. Parameterization grid is improved to parameterize any substring of a parameter. Previously, Find and Replace feature was capable to replace only the entire recorded value of the parameter. Now, you can replace a substring of the parameter. In prior versions, the drop-down "Find What" displayed the entire read only parameter values, when "search by value" box is checked. In this version, the drop-down was changed to a combo box where you can edit the search substring. In the example below, the recorded substring "99" of the parameter value "Logon99" will be replaced by an extractor {{LoginID}} in all requests after clicking "Replace All" button.

5. "Find session by content" for replayed sessions. Often a specific recorded value, such as a token or ID should be replaced by a dynamic parameter. The best way to assure that the recorded value is replaced in all requests, is to confirm that no replayed session contain such recorded value. For that purpose, in Verification Tree, "Find session by content" functionality is added to search replayed sessions after verification.

Analyze results

6. Query test log by session time range. Session time range is a new test log selection criteria. You can select sessions sent within a specific time range, received within a specific time range or combination of thereof. The time range is specified by From / To boxes with number of seconds from the beginning of the test.

7. Show sessions sent or received during the time range selected on the graph. To show sessions sent / received during the selected time range on the graph , select the range to zoom it to the full graph and click "show sessions" button on the toolbar. Sessions sent or receive during this time range will be displayed in the session grid.


8. Port remapping. In the host remapping dialog, an option to remap the recorded port is added. It enables to record a test case against the host listening on the port other than 80 (or 443 for HTTPS) and then target a different port during load tests.

<target host>[:<target port>] <space or tab>  <recorded host>[: <recorded port>]

If the port is not specified, then for HTTP will be used port 80 and for HTTPS will be used port 443.


9. Updated browsers list. The list of emulated browsers was updated to the latest versions of the popular browsers (Internet Explorer, Firefox, Chrome and Opera). Browsers that are no longer in circulation were removed.


10. If StresStimulus is uninstalled before deactivating serial number, then the same serial cannot be used on a different machine. For user convenience, uninstaller now will deactivate the license, if it was activated.




11. Improved autocorrelation capabilities, so less manual configuration is necessary and the Verify process will encounter fewer errors.

12. Improved performance of test loading and initialization.

13. In enterprise version, when checking connection to the SQL Server database, check connection not only from the controller, but also from the agents.

14. Removed inconsistency with session numbering. Previously session numbers in the script where zero-based, but everywhere else where one-based. Now sessions are one-based in the script as well.


Multiple bugs, including all the bugs reported by the community were fixed.

To navigate to other parts of the v3.0 release notes, click the links below:

StresStimulus 3.0 beta is available here.

blog comments powered by Disqus