When a test is stopped AgileLoad Starter automatically moves to Results Analysis. All of the functions here have been covered in the section above. The difference being that as the test is stopped the results are no longer live, they are historical.
Create Report is the final step. At this point the analyst can either generate a report of the results based on an existing report template or create or edit a template tailored for individual needs. Report designer is not covered in this section and will be covered in the advanced section.
Clicking the Generate Report button will create a report based on the last template that was selected in AgileLoad Center, or the default report that is installed with Agile Load.
In order to generate a report Microsoft Word must be installed on the same machine.
Report generation is very fast and should take only a few seconds to complete. As the report is being generated a progress window will pop up, once the report is complete it will appear minimized in Microsoft Word. Maximize word to see the report and its content.
The report shown above is the AgileLoad Report Template. It contains several sections with descriptions of what each section is showing.
The most relevant sections are:
The Summary which has fundamental information such as the configuration of the test, the time and duration of the execution and the numbers of users simulated etc.
The Story Board which shows the scripts in graphical format. Each script that was part of the test will have its own story board entry in the document. This is useful for readers of the report to understand the context of the test and what the simulated users were doing in the test.
Transaction Rates are a definitive way to understand if the application can manage the performance requirements set by the business, for example whilst under a load of X users the system must be able to process Y transactions (such as checkout, or search) per second or per hour.
Pages - Response Time Over Time: As with Transaction rates these metrics are available for analysis during and after the test in AgileLoad Test Center (see next section). This information is particularly important to understand how the system performance is while under load. One of the main goals of performance testing is to understand user experience and hence page load time. This graph plots response time with virtual users, that way it is easy to see if a limit has been reached during the test.
Response Time Distribution allows a breakdown of all the transactions or page load times in the test. If service levels are in place such as ‘90% of all user transactions must be services within X seconds’ then this graph will help evaluate whether that level has been breached or not during the test.
Infrastructure Monitoring can be added to these reports by editing them in the report template designer, covered in the advanced section.
Next Analysis & Reporting with Agileload test center