Skip to end of metadata
Go to start of metadata

New Features and Improvements

Monitoring Windows Server Infrastructure Over the Web 

  1. Monitoring Windows servers via Web. Previously, StresStimulus controller was able to monitor only local servers connected via LAN. Now infrastructure performance monitoring is expanded to Windows servers on the Internet.     

  2. Performance monitoring agents. These remote server agents provide firewall-friendly monitoring of Windows performance counters of any server on the web. 

  3. Multiple server monitoring graphs. Added support for displaying Windows server performance counters on multiple graphs. Previously, all performance counters for all Windows servers were displayed on a single graph. Now you can better customize your performance metrics presentation.     

  4. Performance counter templates to simplify adding machine monitoring. When creating a graph, use templates to quickly add essential counters. 

  5. Dynamics CRM performance counters. Two new counter templates were added to monitor Dynamics CRM performance and register possible failures. 

  6. Customizable names for graphs and machines. Previously the graph name was unchangeable and machine name was its IP address. In this version, you can assign a name to any graph and machine. You can even have the same machine display different names for different graphs.   

  7. Performance counters description. Performance counters' property grid now displays a detailed description of each counter.   

  8. Curve grid sorting. Now test results curve grids can be sorted by clicking the curve name or numerical column headings to simplify graphical data analysis. 



    Enhanced Test Designer for Higher Productivity

     

  9. Autosave/Recover. If the StresStimulus process unexpectedly terminates, upon relaunch, it will ask if you want to restore the autosaved test you were working on.
  10. Comments. Now you can annotate pages, transactions and requests by inserting a comment before or after the object. Comments can be created during recording a test case or at a later time.  
  11. Enhanced search-and-replace operation for creating parameters. Now you can use Regular Expression and Wildcards to search requests and replace recorded values with variables. This option is available in the Parameterization Editor and Free Format Request Editor.     

  12. Simplified creating multiple parameters. Now we can create multiple similar parameters in requests' Url and Body by performing a single expression search / bulk replace operation. In previous versions, you needed to perform two expression search / bulk replaces operations: one for URL and one for body.

  13. Programmatic access to datasets from scriptable variables. Scriptable variables now can access datasets. One example of how this can be used is to emulate javascript actions in the browser.    

  14. Test Wizard auto configuration. If a test case uses transactions instead of pages, then the Test Wizard automatically adjusts its Think Time step to setup think time for transactions instead of pages.  

  15. Easier extractor handling. When opening an extractor for editing or reviewing, an extracted value is already highlighted in the response window. In previous versions, to achieve the same result Verify Extractor operation had to be invoked.  

  16. Now you can double-click and edit a parameter in the Extractor Tree. In previous versions, to edit a parameter in the extractor tree you needed to navigate to the Test Case tree first.
  17.   Simplified the Double-recording correlation method. Now when comparing the same session from two recordings of a test scenario, the sessions are displayed in a grid indicating their URL and size. This allows to save time on manual matching. In the previous version, if automatic matching fails, manual matching was not as user-friendly. 
  18. Quick Verify persistence. If you select the Quick Verify option, it will persist for future verifies.  

  19. Addressed an issue with a preview browser component crashing while replaying certain scenarios. 

    Enhancements in Recording Scenarios

     

  20. Automatic proxy troubleshooting. If your recording proxy is not configured properly, proxy-checker will display troubleshooting instructions.   

  21.  Event log in the recorder.  Now you can quickly troubleshoot issues with recording scenarios. The event log will register detailed information about exceptions with host connectivity, proxy authentication and certificates generation. 

  22. Automatic proxy authentication on recording. if your test machine is connected to your application via proxy that requires authentication, then during recording the proxy credentials cached on the test machine will be supplied automatically. 

  23. New, more reliable recording proxy in standalone version. New recording proxy is compatible with almost any upstream proxy that can possibly exist in the Enterprise network environment.

  24. Support recording in Google Chrome v58+ and Firefox v48+. New versions of Google Chrome and Firefox browsers require different types of certificates for recording HTTPS traffic. Support for such certificates was added.

  25. Updated Excluded Hosts in the test wizard.

  26. Updated Excluded Content-Types in the test wizard.

  27. In the test case, include or exclude requests with 401 HTTP status-code 

  28. Promptly delete or keep unwanted hosts and content-types that the user selected in the Test Wizard but did not delete./

  29. Added support for Fiddler v 4.6.20172, released on Jul-20-2017.
  30. Addressed an issue with recording scenarios using IE 11 on Windows 8+. StresStimulus detects when IE runs in AppContainer Process which blocks recording, and fixes the issue by enabling loop-back. 



    New Options for More Realistic and Reliable Load Testing

     

  31. Default Goal (s) for Transactions. Now when you set a default goal, it effects not only pages, but also transactions.  
  32. Quick Goal setting on a Test Case level. Now you can set a goal for all pages and transaction by changing it in one Test Case property.        
  33. Option when to request transaction. Transactions can now selectively run only the first iteration or last iteration. This can be helpful to perform initial or final actions, such as log ins / log outs.  
  34. Think time between transactions. Added a test case property to handle think time between transactions, similarly to how it was done for pages.     

  35. The default timeout for a test case sets the same timeout for all requests. Previously it set the same timeout for pages. The new approach is more consistent and reliable.
  36. In previous versions, the validator's Text to search property was used to identify errors in test results. In this version, the Description property is used for that, which helps to create more readable and customized reports. 
  37. Updating datasets. In prior versions, datasets had no connection to the original data source. As a result, datasets could only be updated by manually deleting the data and copying/pasting new data from an outside source, such as Microsoft Excel or other grid-based data array. In this version, datasets created from an external data source can be reloaded with fresh data from the source. 
  38. Better graphs presentation. In the previous versions, minimum graph range was 100. In this version, due to improved auto-scaling, graph ranges start with 0.1. As a result, graphing of small values is more readable.
  39. Test results Summary View now displays a complete list of transactions from slow to fast, each of which is hyperlinked to a transaction sub-report.

    Other Enhancements

     

  40. Added support for Fiddler v 4.6.20172, released on Jul-20-2017.
  41. Added support for UHD monitors.
  42. In External report added screenshots for  transactions.
  43. Ability to edit parameters in the extractor tree.
  44. Numerous minor enhancements and internal fixes

 

  • No labels