Skip to main content

The Build Detail Page

Central place to know "What do we know about this deployment?". A complete picture of testing against a specific build, including summary statistics, all test plans, defects found, risk coverage, and deployment information.

Overview

Click any build version from the Builds list to open its detail page. The page is organized into several sections:

  • Header with build information and action buttons

  • Summary statistics cards showing results at a glance

  • Test Plans that ran against this build

  • Defects found during testing

  • Risk Coverage information (if your project uses risk-based testing)

  • Work Items (if Azure DevOps is connected as your requirement manager)

  • Deployment or Build Details card on the right side

Summary Statistics

At the top, you see cards with key metrics:

Results Against Build

Shows the total count of test case executions against this build. The bar is divided into colored segments: Passed / Failed / Blocked / Skipped / Not Run

This gives a quick visual sense of the build's test health.

Passed

Shows the number and percentage of test cases that passed. For example, "245 (87%)" means 245 test cases passed, accounting for 87% of all executed cases.

Failed

Shows the number of test case failures. Next to this is the count of defects raised from those failures. For example, "34 failures, 28 defects" means 34 test cases failed, and the team opened 28 defect tickets.

Risks Covered

This card appears only if your project uses Risk-Based Testing. It shows how many high and critical risks were exercised by test cases executed against this build. For example, "15 of 18 high risks covered" means your testing addressed 15 out of 18 high-level risks.

If some high or critical risks were not tested, a warning message appears: "N high risks not covered."

Work Items / Defects in Build

Shows the count of work items (requirements) exercised by test cases in this build, broken down into open and closed defects.

Test Plans in This Build

A table showing all test plans linked to this build:

Column

What It Shows

Plan

The test plan name and display number; click to open the plan

Cases

How many test cases are in the plan

Last Executed

The most recent date this plan was run

Results

A progress bar showing passed, failed, blocked, not run, and unexecuted cases

Status

A badge indicating overall status

Use this table to drill down into specific plans and see their details and results.

Defects Found

If defects were raised during test execution against this build, a table shows:

Column

What It Shows

Defect

The defect title and ID; click to view the full defect

Found In

Which test plan discovered this defect

Status

Whether the defect is open, in progress, or closed

This lets you quickly identify and prioritize issues discovered in this build.

Risk Coverage (Risk-Based Testing Only)

If your project uses Risk-Based Testing, this section displays each risk with:

  • Risk level - Critical, High, Medium, or Low, shown with a colored badge

  • Risk title

  • Covered status - either "N cases run" if it was tested, or "Not covered" if it was not

High and critical risks that aren't covered display a warning banner at the top, prompting the team to add test cases for those risks.

Work Items (Azure DevOps Only)

If Azure DevOps is connected to your project, this section shows all work items (requirements) that were exercised by test cases executed against this build. Each work item displays:

  • The work item title and ID

  • The test cases that are linked

  • The execution status (passed, failed, blocked, etc.)

This provides traceability from requirements through to test execution.

Deployment Information vs Build Details

On the right side of the page, you see one of two cards:

Deployment Card

This appears if the build was created via a CI/CD pipeline using the tc createBuild CLI command. It shows:

  • Version - the software version

  • Commit - the Git commit hash; click to view on your repository

  • Repository - the repository URL; click to visit it

  • Deployed - the date and time of deployment

  • Release - the release this build is part of

  • Environment - the deployment environment

This information comes directly from your CI pipeline and provides full traceability from code commit to test execution.

Build Details Card

This appears if the build was created manually in TestCollab (without CI data). It shows:

  • Version - the software version you entered

  • Environment - where it was deployed

  • Release Date - when it was deployed

  • Added - when the build was created in TestCollab

  • Release Notes URL - a link to release notes if provided

  • Notes - any notes you entered when creating the build

Assigning or Changing the Release

On the deployment or build details, there is a Release row.

  • If you are a Manager or Admin, you see a dropdown allowing you to assign or change which release this build belongs to. Select from the list or click the current release to unassign.

  • If you are a Tester or Viewer, you see the release as a blue chip (clickable link to the Release Readiness page).

If the release was manually assigned you'll see a "Manually assigned" label when you hover, indicating it was not auto-linked.

Related Articles

Related Articles
Did this answer your question?