Analyze build trends

Use the Build Summary page to evaluate build health in a release. For example, use the widgets to draw conclusions about the following questions:

  • Are defects being worked on by severity?
  • How is the development effort shared between defects and user stories?
  • Identify unplanned work: what percentage of changes are not assigned to either user stories or defects?
  • How stable are the builds?
  • Is new code being tested?

Note:  

All build information on the page is specific to a release and filtered by several parameters.
  • Make sure the correct release is selected.
  • Select an application, build type or configuration, and time period.

  • Determine whether you want to display failed builds and downstream builds. If you do not select downstream builds, only root builds are displayed.

Data aggregation: Metrics for parent builds display aggregated data of their downstream builds.

The Build Summary page displays the following widgets:

An overall summary of the build success rate and the average build time.

Select a build number to view detailed metrics. Drag the slider at the bottom of the timeline to view earlier or later builds.
  • View the build status along the top row of the timeline .

  • Find correlations in builds between pairs of metrics. The metrics are displayed as bars on the timeline.

    Use the dropdown menus to select any two of the following metrics:

    Code Changes The number of lines of code changed in the build. The code changes are broken down by their association with user stories, defects, or neither.
    Code Coverage The percentage of code in the build that is covered by unit tests.
    Test Success The success rate of unit tests run on the build.
    Worked on Defects by Severity The number of defects worked on in the build, broken down by severity.

    Example: Possible correlations:

    Test Success - Code Coverage: If the test success is stable, but code coverage is declining, the test success is not very informative.

    Code Changes - Code Coverage: If code changes are made but the code coverage is in decline, developers are not creating tests for their code.

    Code Changes - Test Success: If code changes are made but the test success rate is dropping, the new code may be breaking existing features.

View detailed information about a build.

In the builds timeline, select a build and specific metrics to display.

More options:

View metrics for a range of builds Select another build from the Build Impact dropdown to create a range. For details, see Review a build range report.
Display full build details Click View Report. For details about the data shown here, see View build report.

Display build server statistics

Click Build System Details.

Compare key statistics for all builds, such as unit test success rate, code coverage percent, and number of files and lines affected by code changes in the build.
  • Click a column header to sort the table.
  • Click a build number to open a build report.