Load Test Perspective
When a load test is executed and the results are published, the details of load test results at the page, transaction, and counter levels are loaded into the data warehouse and appears in the Result perspective. By using these details, you can answer questions such as:
Which transactions and pages were executed in the load test, and what was their average response time?
What counter values, such as memory usage or network throughput were collected, and what were the values?
Are the results of a particular load test better or worse than results from a comparison test?
Note
In order to use perspectives with the Team System cube, you must use Microsoft SQL Server 2005 Enterprise Edition or SQL Server 2005 Enterprise (64) Edition on the data tier. SQL Server 2005 Standard Edition that ships as part of Team Foundation Server, does not support the use of perspectives. When using SQL Server 2005 Standard Edition, the cube elements from all perspectives reside in the Team System data cube.
Measures
The following table describes the measures that are included in the Load Test perspective. The information that is contained in the measures and dimensions for this perspective are driven by the structure of the load tests that generated the results that have been published to the data warehouse. For more information about the various counter values, see Test Results Reported.
| Measure | Measure Group | Description |
|---|---|---|
Value |
Load Test Counter |
Values collected by the counters during the execution of the load test. These values can be analyzed using the attributes in the Counter ID dimension. Depending on the type of counter that is taking the measurement, the value in this measure has different meanings, for example, the amount of available memory, the number of requests per second, and so on. |
Average Duration |
Load Test Details |
The Average duration for the tests executed during the load test. |
Failed Tests |
Load Test Details |
The number of tests that failed during the execution of the load test. |
Total Tests |
Load Test Details |
The total number of tests that were executed as a part of the load test. |
Page Count |
Load Test Results |
The number of Web page reads that occurred in the load test. |
Response Time |
Load Test Results |
The average response time for the pages read by the load test. |
Actual Duration |
Load Test Summary |
The actual duration for which the load test ran. |
Elapsed Time |
Load Test Transaction |
The average elapsed time for the transactions that occurred in the load test. |
Load Test Transaction Response Time |
Load Test Transaction |
The average response time for the transactions that occurred in the load test. |
Transactions |
Load Test Transaction |
The number of transactions executed during a load test. This can be summarized by the transaction dimension. |
Dimension
The following table describes the attributes that are included in the Load Test perspective. You can aggregate the measures along each of these attributes.
| Attribute | Dimension | Description |
|---|---|---|
Build |
Build |
Number or name used to uniquely identify the build. |
Build Start Time |
Build |
Date and time the build began. |
Build Type |
Build |
Name of the build type. Set in the New Team Build Type Creation Wizard. For more information, see How to: Create a New Build Type. Selected from the Team Builds node in Team Explorer. For more information, see How to: Run a Build on a Build Type. |
Counter |
Counter ID |
Identifies the specific counter within the counter object to which the Value measure in the Load Test Counter measure group is associated. For example, for the Request counter object, the values contain elements identified by the specific counter such as Average Response Time, Cached Requests, Failed Requests, and so on. |
Counter Instance |
Counter ID |
Identifies the counter instance associated with the Value measure of the Load Test Counter measure group. For example, a counter instance may indicate a specific network card associated with the measurement of Bytes Received per second, Counter within the Network Interface counter object. |
Counter Object |
Counter ID |
The Load Test Counter object used in measuring activity during the load test. This includes counters such as Memory, Network Interface, or Requests. These counters relate to the Value measure in the Load Test Counter measure group described above. Finer granularity for interpreting the meaning of this attribute is contained in the Counter attribute of the Counter ID dimension. |
Counter Result |
Counter ID |
Boolean value indicating that the current counter is used to determine the overall result. |
HigherIsBetter |
Counter ID |
A flag indicating whether the value measured by this counter instance is better when the value is higher. For example, it is better to have higher throughput for the Bytes Received per Second counter, but it is not better to have higher memory consumption for the Average Test Time measurement. This enables reports to be created that indicate improvements from one run of a load test to another. |
Load Test Counter Dimension |
Counter ID |
Used internally. |
Load Test Scenario |
Load Test Scenario |
The scenario used for measurements found in the Load Test Transaction and Load Test Details measure groups. |
Load Test Transaction Dimension |
Load Test Transaction |
Used internally. |
Transaction |
Load Test Transaction |
The name of the transaction associated with measurements in the Load Test Transaction measure group. This enables a list of all transactions, and their corresponding response times and frequencies to be generated for a particular load test result, or across many load test results. |
Machine |
Machine |
The computer on which the associated load test counter collected information. |
Load Test Page Summary Dimension |
Page Summary |
Used internally. |
Url |
Page Summary |
The URL of the Web page used when measuring the Page Count and Response Time measures of the Load Test page Summary measure group. |
Result |
Result |
The name of the Test Result of the load test. By default, this is the timestamp of the time at which the load test was run. |
Test |
Result |
The name of the load test. |
Test Description |
Result |
A description of the test when the load test result was run. |
Test Type |
Result |
The type of test associated with the test result. For load tests, this will always be Load Test. |
Run |
Run |
The description of the test run that produced the load test results. |
Remote Run |
Run |
A True/False flag that indicates if the test run that produced the load test results was a remote test run. |
Load Test Scenario |
Scenario |
Used internally. |
Team Project |
Team Project |
The team project referenced when publishing the load test results. |
See Also
Concepts
Other Resources
Understanding the Structure of the Data Warehouse Cube
Perspectives