xp-toronto Analytics
| xp-toronto The upcoming release of the xp-toronto site. |
Summary | ||
| System - Activity How much testing activity is occurring? Daily summary and trends for project's principals, test runs and added tests. |
 |
|
| Operation - Summary How does this weeks activity compare with the average? This weeks and last weeks daily activity are compared against the average week day by day. |
 |
|
Unit Tests | ||
| Unit Tests - Broken Test Duration How long does it take to fix a broken test method? Broken tests are expected, but the number triggered by each change and the corresponding time required to fix them is related to the quality of the code and the development process. |
 |
|
| Unit Tests - Code Coverage Details Display detailed coverage information of code coverage for all the packages and classes of a project for analysis. A number of charts summarize this data in alternative ways. |
 |
|
| Unit Tests - Code Coverage Summary How much code coverage are the tests generating and where should the team focus their efforts to improve it. |
 |
|
| Unit Tests - Distinct Test Methods How many test methods are defined for the project? A healthy increase in test methods corresponds to continued development of new functionality. View the total distinct test methods and changes day by day together with trends over time. |
 |
|
| Unit Tests - Test Method Duration How long does it take to execute a test run? Excessive durations for test runs dissuades developmers from active testing and complicates frequent integrations by team members. The time taken to execute test methods is broken down by package then class. |
 |
|
| Unit Tests - Test Method Names Summary of the names of test methods and the words they are composed from. Method names are important to communicate the intent of a test for later maintenance and can indicate the features and focus of the system. |
 |
|
| Unit Tests - Test Methods Executed How many test methods were executed each day? View the total number of test methods executed each day together with trends over time. The aggregate success and failures rates are also shown. |
 |
|
| Unit Tests - Test Results What was the failure rate for test method executions? The failure rate is broken down by package then class to reveal recently written code or code that repeatedly fails. |
 |
|
| Unit Tests - Test Runs Executed How many test runs were executed each day? View the total number of test runs executed each day together with trends over time. |
 |
|
Code | ||
| Code - Dependencies Dependency information for software subsystems. Depicts a graphical snapshot of the current dependencies as a graph and matrix together with historical forms. |
 |
|
| Code - OO Design Quality Object-Oriented design quality metrics. Snapshot of current coupling, instability, abstractness and main sequence values for the project together with temporal trendings. |
 |
|
| Code - Summary Metrics related to the software code and trends over time. Include lines of code, average sizes of program elements and other standard code measures. |
 |
|
Issue Tracking | ||
| Bugzilla - Summary Summary of the trends and current state of issues from the Bugzilla issue tracking system. Breakdown bugs by priority and severity. Indicate trends in issue tracking activity. |
 |
|
Research | ||
| Research - Day of Week Does the day of the week have any effect on testing activity and the development process? View a number of testing metrics arranged on a day-of-week spider graph. |
 |
|
| Research - Effect of Test Duration Does the duration of executing test runs have any effect on the development process? Investigate whether there is any connection between the time to run all the tests and a number of other development metrics. This comparison is plotted for each of the included projects. |
 |
|
| Research - Hour of Day Does the hour of the day have any effect on testing activity and the development process? View a number of testing metrics arranged on an hour-of-day spider graph. |
 |
|
| Research - Unit Test Correlations What are the strongest correlations between the various testing metrics? List out a number of the collected metrics for a project with the correlation value for each pair of metrics. |
 |
|
Instrumentation | ||
| Instrumentation - Operation Usage How is the DevCreek application itself being used? Historical summary of the use of features and modes within the system by users. |
 |
|
| Instrumentation - Performance Diagnosis Support diagnosis of performance results by breaking down the worst performing actions as a call hierarchy. |
 |
|
| Instrumentation - Performance Summary Summary of performance data collected from a running system to aid recognizing hotspots and trends over time. |
 |
|
| Instrumentation - Performance Trends Depict trends in the times of performance actions for the entire system and for the worst performers. |
 |
|
Miscellaneous | ||
| Dashboard - Development Team Overview of recent activity on the project intended for daily or weekly review by the development team. |
 |
|
| System - Principal Statistics Which principals have been used to submit data to the project? Simple tally of the number of principals and sessions recorded by the server. |
 |
|
| System - Record Statistics How much data is being submitted to the server for a project? Simple tally of the different types and volume of data submitted to the server from agents. |
 |
|