"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 » Testing Your User Journey » Analysing the Results of a Quick Run

« Execute a Quick Run | Adding Parameters »
 

Analysing the Results of a Quick Run

  • When you click “OK” to start the Quick Run, StressTester™ will switch to the Analyze Results workspace. (You can ignore the prompted video tutorial at this point – this workspace will be covered in greater detail later in this tutorial.)
     
  • You will see that the running User Journey is selected in the navigation tree, the screen is set to refresh every 5 seconds and, once the User Journey starts to execute, results will appear in the graphs and data tables in the right-hand panel.


    Inspect Application Response

  • On the far right-hand side of the screen you will see thumbnails drawn from top to bottom as the Quick Run progresses. Each thumbnail represents a web page returned by the application.
     
  • To see a thumbnail displayed in full in a browser, double-click on it and the web page received by StressTester™ during the Quick Run will be shown in your default browser.


    Inspect Errors

  • At the bottom left of the screen you will see a “Details” box. This shows you the start time of the test, its duration and most importantly whether any errors have been detected.
     
  • If errors are detected, you should click the “Details” button to view the errors. Errors due to HTTP response codes are indicated by having a value in the “Error Code” column. (Due to a quirk HTTP errors are reported twice in this window, yet only once in the summary display.)
     
  • To see further details of the error, hover over the Message and the full details will be displayed.
     
  • It is not unusual to find errors such as HTTP code 404 (resource not found) reported. Even the most famous and popular of web sites often have small images, cascading style sheets or other resources missing!
     
  • If you do detect 404 errors or others that indicate a problem with your application, you can leave the corresponding requests in your User Journey (you will continue to receive errors until the application is fixed), or identify the requests that cause the error and remove them from the User Journey (to delete a step, select it in the User Journeys workspace, right-click and choose “Delete”).

     
  • We will not look at the response times at this stage of the tutorial. Full analysis of test results is covered in a later section. 

« Execute a Quick Run | Adding Parameters »
 

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