Once your project is created as desired, to run the project, click Project -> Start... in the menubar. AppPerfect Load Test will automatically switch the UI to the "Status" tab. This view displays the status of your test in real-time. Data is refreshed periodically based on the "Refresh Interval" defined in Tools -> Options... -> AppPerfect. Key data points such as Response Time, Virtual User Count, Hit Count, etc. are displayed in this view.
The Status tab allows you to monitor the progress of the test and witness the dynamic variations across different factors which affect your application being tested.
You can view the status panel during the test run with dynamic values and once the test run has completed, it shows similar details as the Result tab but you will get more comprehensive information about the results of the completed test in the Result tab.
The Status tab represents information using charts and tables.
You can see the following charts for:
This chart displays the hit counts at different points of time of the URL group execution. This chart helps you determine when the number of failed/timed out requests started increasing and this information can be used in conjunction with the User Count chart to find out the approximate point where the load is not being handled effectively by the application.
The X-Axis displays the time stamps at regular intervals since the start of the URL group. There are six values plotted against the Y-Axis. The one shown in green color indicates the number of successful hits at that point of time, the one shown in red color indicates the number of failed hits and the one in orange color indicates the number of requests that have failed due to time-out.
This chart displays the wait periods at different times and also gives a summary of the maximum, minimum and average wait period that help you get an insight into how long would it take a visitor to receive a page.
The X-Axis displays the time stamps and the Y-Axis has values plotted for the maximum, minimum and average wait periods for that interval. This information in conjunction with the Hit Count can help determine the number of users that can safely access the application simultaneously, without too much of a degradation in service.
This chart shows the number of users at different times during the test and help you gauge the kind of load that the application can tolerate. The X-Axis of this chart plots the time stamps at regular intervals while the Y-Axis plots the number of users at that time. When compared with the Response Time chart and the Hit Count chart, it gives you important information about how your system is reacting to the load and helps you set the tolerance levels of your application.
This chart shows the number of bytes of data received as response from the server by the application. The X-Axis of this chart plots the time stamps at regular intervals while the Y-Axis plots the number of kb of data received at that time. When compared with the Response Time chart and the Hit Count chart, it gives you information about how much response data is being sent to users with respect to hits and response time.
The same charts apply to Database projects.
The following tables can be seen:
The status table shows group-wise current state of the test as property:value pairs. The Status property indicates if the test is running, paused or completed. Result is shown as successful until any of the request fails. The Elapsed Time shows the time since the start of execution for that URL group. The Actual Duration shows the time the request group has been executing. The difference between the two is that when a test is paused, the elapsed time will include the pause time while the actual duration will ignore it meaning that if there is no pause during the execution of the test, then both the time values will be the same. The Current Users shows the number of threads that are currently firing the requests. Failed Hits indicates the total number of requests that have failed till now while timed out Out Hits depicts the total number of requests that have timed out. Total Hits shows the number of requests that have been processed so far. Average Response Time is calculated using the minimum and maximum response times.
This table provides details about the user activity recorded in the test. It comprises of tabular information about the users such as User ID and Name, number of Successful, Failed and Timed out hits, Start and End time, and the Status of the request.
This table provides details about each virtual user activity recorded in the test. It comprises of tabular information about the virtual users such as User ID, number of Successful, Failed and Timed out hits, Start and End time, and the Status of the request.