"We’ve found that StressTester™ is very easy ...

we proved that the results it supplies are the same as the industry leader."

Darrall Pullen, CTO, PPG

"StressTester™ provides Tescom with a more Agile approach – we are able to reduce the time between test design and execution"

Marco Venzelaar, Tescom UK

"A job that would take 10 days to prepare in other tools, takes 2 or 3 days with StressTester™"

Head of Testing, Mission Testing

"There is no limit in functionality – it covers all that products 10 times its price provide!"

Darrall Pullen, CTO, PPG

"One of the strongest pros for StressTester™ is Reflective Solutions’ unprecedented customer support"

Will Smithee, Questcon USA

StressTester™ Learning Center - Tutorials

» Tutorials » Analysing Performance Test Results » How Did Performance Change as Load Increased?

« Analysing your Test Results | Which User Journeys Were the Slowest? »
 

How Did Performance Change as Load Increased?

  • Select the performance test you wish to analyse in the Run Name window of the Analyse Results workspace navigation panel.
     
  • Select all User Journeys that executed during the test within the User Journeys and Monitors window of the navigation panel.
     
  • If the test is running, the Refresh field will be available.  if it is, enter a value of 5 seconds.
     
  • Click the button alongside this field, either “Show Results” (for a test that has completed) or “Refresh”.
     
  • The right-hand side of the workspace will now show the performance test results for the selected User Journeys in the selected performance test.
     
  • If it is not selected, select the Avg Response per Sec tab in the top half of the screen, and look at the displayed graph.
     
  • This graph shows the response times of web pages, calculated per second, for the selected User Journeys.  In addition, the black line shows how load increased during the test.
     
  • If you see that the average response times of any of the User Journeys increased as load increased, you will have identified the User Journeys that experienced a performance degradation during the test.
     
  • Other graphs show you the average response times calculated per minute (useful for longer running tests), the number of requests made (so you can see if there were any application bottlenecks), and errors. 
     
  • You will see later on how you can configure as many different graphs as you like; the default StressTester™ Trial download contains only a subset of what is available and the whole screen is completely customisable so you see the information you need in the format you wish.
     
  • HINT: If you want to view more than one graph at a time, right-click on the graph tab, select Open in New Window and then the graph will be displayed in its new window.  You can also do this for data tables.
     
  • This facility is possible during a performance test as well; you can see that the screen shot below shows the average response times compared to the number of requests, which web pages are performing the slowest, and compares the maximum, average and minimum response times of a User Journey’s web pages – all on the screen at the same time!

    StressTester™ graphs

 

  • Even if none of your User Journeys degraded during this test, it is recommended you go through the following sections to understand how you can obtain much more information within this workspace.
     

« Analysing your Test Results | Which User Journeys Were the Slowest? »
 

Not seeing the StressTester™ information that you need - please email Support.