Delete Test Results
1. Open a Test and click the Results tab of the Test Pane.
2. Click , in the toolbar.
3. In the Delete Test-runs dialog box, select the Test-runs you want to delete.

Test Audit Log
The Test Audit log contains a list of significant events that have occurred during a Test-run. These include the times and details of Test initiation and completion, errors that may have occurred and Virtual User details.

Additional Audit log entries may be written to the log if the Scripts included in the Test have been modeled to incorporate the appropriate SCL code. Use the LOG SCL command in a Script, to generate the data content for the Test Audit log.

Test Report Log
The Test Report log is a sequential text file that is used to record information about a single Test-run. Usually, a single record is written to the Report log whenever a Test case passes or fails.
Additional Report log entries may be written to the log if the Scripts included in the Test have been modeled to incorporate the appropriate SCL code. Use the REPORT SCL command in a Script, to generate the data content for the Test Report log

Test History Log
The Test History log is a sequential text file that is used to maintain a chronological history of each occasion on which the Test was run, together with the results of that Test. Usually, a single record is written to the History log when the Test-run is complete.

In addition, further Test History log entries may be written to the log if the Scripts included in the Test have been modeled to incorporate the appropriate SCL code. Use the HISTORY SCL command in a Script, to generate the data content for the Test History log.

Test Error Log
The Test Error Log records all significant error messages from the Test Manager, Task Group Executers and OpenSTA Daemon.
Data included in the log are: Time Stamp, Test Name, Location and Message.

HTTP Data List
The HTTP Data List stores details of the HTTP requests issued by the Scripts included in a Test when it is run. This data includes the response times and codes for all the HTTP requests issued. The amount of HTTP data recorded depends on the Logging level specified for a Script-based Task Group when you created the Test and defined the Virtual User settings to be applied. The Logging level setting controls the number of Virtual Users that statistics are gathered for and can be edited from the Configuration tab of the Test Pane.

The data is presented in a table and can be sorted by clicking on the column headings to reverse the display order of the data entries. These results can also be filtered by right-clicking inside the table and selecting the Filter option. Use the Export right-click menu option to export data in .CSV text file format which allows them to be imported into other data analysis and report generating tools.

HTTP Data Graphs
The volume of HTTP data recorded is controlled by the Logging level you set for a Task Group's Virtual Users. The Logging level determines the number of Virtual Users that data is collected for and controls the quality of the data displayed in the graphs. The HTTP data collected relates only to responses to HTTP requests issued as part of Test.
The HTTP data collected during a Test-run can be displayed in a number of different graphs where you can scrutinize your Test results. There are seven graphs in total which you can display using the Results Window.

HTTP Response Time (Average per Second) v Number of Responses Graph
This graph displays the average response time for requests grouped by the number of requests per second during a Test-run.

HTTP Errors v Active Users Graph
This graph is used to display the effect on performance measured by the number of HTTP server errors returned as the number of active Virtual Users varies during a Test-run.

HTTP Errors v Elapsed Time Graph
This graph displays a cumulative count of the number of HTTP server errors returned during the Test-run.

HTTP Responses v Elapsed Time Graph
This graph displays the total number of HTTP responses per second during the Test-run.

HTTP Response Time v Elapsed Time Graph
This graph displays the average response time per second of all the requests issued during the Test-run.

HTTP Active Users v Elapsed Time Graph
This graph displays the total number of active Virtual Users sampled at fixed intervals during a Test-run.

Single Step Results
During Test development it is important to check that a Test runs correctly. You can run a single stepping session to help verify a Test by monitoring Task Group replay to check that the WAE responses are appropriate. Then use the Single Step Results option to analyze the results data obtained. The data includes the HTTP requests issued to a target WAE and the HTTP returned in response during a single stepping session.

Single stepping a Test is a useful method to help you verify that a Test with a modular structure runs as you expect. A modular Test incorporates two or more Scripts in one Task Group to simulate a continuous Web browser session when the Test is run and requires some modeling of the Scripts included. After single stepping the Task Group that contains the Script sequence, open up the Single Step Results option and double-click on an HTTP request to display the request details.

View the details of the HTTP request in response to which the first cookie was issued during a Test-run. In the Response Header section of the Request Details window look for the Set-Cookie entry and make a note of the cookie ID including its name and value. Then view first request included in the next Script in the sequence and look in the Request section of the Request Details window for the Cookie entry. The cookie ID recorded here should be the same as the first cookie value issued at the end of the previous Script. Ensure that the value of the last cookie issued in each Script is handed onto the next Script in the sequence, for all the Scripts in the Task Group.

Timer List
The Timer List file gives details of the Timers recorded during a Test-run. Timer results data records the time taken to load each Web page specified by a Script for every Virtual User running the Script during a Test-run. The level of Timer information recorded is controlled by adjusting the Virtual User settings in the Test's Script-based Task Groups. Open the Test with the Configuration tab of the Test Pane displayed, then click on a VUs table cell in a Task Group and check the activate the Generate Timers for each page option in the Properties Window. The Logging level you select here controls the volume of HTTP data and the number of timers recorded.

The information collected is presented in a table and can be sorted by clicking on the column headings to reverse the display order of the data entries.

Timer List can be exported to a .CSV text file which allows results to be imported into many other data analysis and report generating tools.

Timer Values v Active Users Graph
This graph is used to display the effect on performance as measured by timers, as the number of Virtual Users varies.
You can control the information displayed by filtering the timers.

Timer Values v Elapsed Time Graph
This graph is used to display the average timer values per second.
You can control the information displayed by filtering the timers

SNMP and NT Performance Collector Graphs

The data collection queries defined in a Collector generate results data that can be displayed in custom graphs. A maximum of two custom graphs are produced per Test-run. All NT Performance Collector data is displayed in the Custom NT Performance graph. All SNMP Collector data is displayed in the Custom SNMP graph.
If your Test includes more than one NT Performance or SNMP Collector, the appropriate custom results graph combines the data collection queries from all Collectors of the same type and displays them in one graph which you can then filter to display the data you require.
Use the Filter option to select and display specific data collection queries defined in the Collectors. The unique names you assigned to each query are displayed below the graph in a color coded key. The IP address of the Host used to run the Collector Task during a Testrun is automatically listed alongside the query name.

Single Stepping HTTP/S Load Tests
Make use of the single stepping functionality provided during Test development to check your HTTP/S load Tests and to help resolve errors that may occur during a Test-run.
When you run a Script-based Task Group within a single stepping session HTTP is returned from target WAEs in response to the Scripts that are executed during replay. You can single step through the browser requests contained in Scripts and monitor HTTP responses to check that the Task Group is behaving as required.

Single Stepping Procedure
Begin a single stepping session by opening a Test, right-clicking on a Script based Task Group in the Test table, then selecting Single Step Task Group from the menu.
The next step is to configure the session so that the Task Group runs as required. Run and monitor the replay then make use of the results generated.