Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate external secret providers
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference

Review test insights

7 minute read

Monitor and analyze test execution metrics through the test insights dashboard to understand testing coverage, identify failing tests, and optimize test performance across components. The dashboard provides comprehensive views of test suite execution, failure rates, and test case performance to help improve code quality and reduce build times.

Use test insights to better understand test execution behaviors, detect and fix components with commonly failing or unstable test results, detect components that have not yet been tested, and determine which test cases take the longest to run so you can optimize them to reduce build times and speed up deployments.

You can view test results from a specific run in the Test results tab of Run details.

Prerequisites

Check the following prerequisites to make sure you have correctly configured your pipeline or workflow to collect test results for populating the test insights dashboard.

Table 1. Prerequisites for populating test insights
Pipeline or workflow type Required configuration to collect test results

CloudBees Unify workflow

Add the CloudBees Unify publish test results action to a CloudBees Unify workflow that executes a test.

GHA workflow

Add the GHA publish test results action to a GHA workflow that executes a test.

Integrated CloudBees CI or Jenkins Multibranch Pipeline

Add a step to your Jenkinsfile for publishing test results.[1]

Use a CloudBees Unify workflow to run a CloudBees CI job

Add the Run a CloudBees CI job action to a platform workflow, and set the test-result-location parameter.

Use a CloudBees Unify workflow to run a Jenkins job

Add the Run a Jenkins job action to a platform workflow, and set the test-result-location parameter.

[1] CloudBees suggests that you use this method if you are running a Multibranch Pipeline, as you can then view your pipeline jobs and builds directly within the CloudBees Unify UI.

Access test insights dashboard

To access the test insights dashboard:

  1. Select Analytics  Test insights.

The test insights dashboard loads with default filtering showing the last seven days of data. If you have already selected a specific component, that selection is maintained.

Filter dashboard data

Use FILTER to select specific components and adjust the time frame (last 7/30/90 days, current/previous week/month, or custom range). By default, the dashboard shows the last seven days of data.

Analyze components, workflows, and runs with test coverage

Get an overview of components, workflows, and workflow runs for the filtered component data in a specified time frame.

The dashboard charts display the following with and without test suites:

  • Components

  • Workflows

  • Workflow runs

Totals of components
Figure 1. Example Components, Workflows, and Workflow runs charts.

Each chart displays the following details (highlighted in the Workflows chart above):

  1. Total number.

  2. A donut chart of those with and without test suites (in percentages).

  3. Numbers of those with and without test suites.

The Components chart also displays the number of associated repositories, and the Workflows chart displays the number of associated branches.

View components test coverage details

To view components test coverage details:

  1. Select a number, or a section of the donut chart in the components chart.

The system displays a list showing:

  • Component name

  • Repository URL

  • Number of test suites

If you select a section of the donut chart, or the with or without test suites numbers, the data displayed is for only that subset of components.

In the list, perform any of the following:

  • Select FILTER to filter by with or without test suites.

  • Search for specific components by entering all or part of any column item into Search.

  • Select Sort down or Sort up next to a column heading to sort on that heading.

  • Select a component name to display its component summary in a new browser tab.

  • Select a repository URL to display the repository in a new browser tab.

View workflows test coverage details

To view workflows test coverage details:

  1. Select a number, or a section of the donut chart in the workflows chart.

The system displays a list showing:

  • Workflow name

  • Component name

  • Branch name

  • Number of workflow runs

  • Number of test suites

If you select a section of the donut chart, or the with or without test suites numbers, the data displayed is for only that subset of workflows.

In the list, perform any of the following:

  • Select FILTER to filter by with or without test suites.

  • Search for specific workflows by entering all or part of any column item into Search.

  • Select Sort down or Sort up next to a column heading to sort on that heading.

  • Select a component name to display its component summary in a new browser tab.

View workflow runs test coverage details

To view workflow runs test coverage details:

  1. Select a number, or a section of the donut chart in the workflow runs chart.

The system displays a list showing:

  • Run ID

  • Workflow name

  • Component name

  • Branch name

  • Run status

  • Number of test suites

If you select a section of the donut chart, or the with or without test suites numbers, the data displayed is for only that subset of workflow runs.

In the list, perform any of the following:

  • Select FILTER to filter by with or without test suites.

  • Search for specific runs by entering all or part of any column item into Search.

  • Select Sort down or Sort up next to a column heading to sort on that heading.

  • Select a run ID to display the run details in a new browser tab.

  • Select a component name to display the component summary in a new browser tab.

Workflow runs filtered
Figure 2. Example Workflow runs list with two filters highlighted.

Review tests overview by test suites

The filterable tests overview lists details of all test suites run. The Test suites view displays detailed information about individual test suites.

To review tests by test suites:

  1. Select TEST SUITES view in the tests overview section.

  2. (Optional) Select FILTER, and then select one or more of the options:

    • Test suite name

    • Component name

    • Workflow name

    • Branch name

  3. (Optional) Search for specific test suites by entering all or part of any column item into Search.

The test suites view displays:

  • Test suite name

  • Component name

  • Default branch name

  • Workflow name

  • Last run date and time

  • Total test cases

  • Average run time

  • Total test case runs

  • Failure rate on last run

Select Sort down or Sort up next to a column heading to sort on that heading.

Review tests overview by components

The Components view displays component-level test aggregations and failure rates.

To review tests by components:

  1. Select COMPONENTS view in the tests overview section.

  2. (Optional) Filter and search using the same options as the test suites view.

The components view displays:

  • Component name

  • Default branch name

  • Workflow name

  • Last run date and time

  • Total test cases

  • Average run time

  • Failure rate (overall)

In the Components view, hover over Failure rate to display the totals of successful test case runs (green bar), failed test case runs (red bar), and skipped test case runs (yellow bar).
Test suites overview
Figure 3. Example Tests overview list.

Investigate test case details

In either view, you can drill down to see individual test case performance details.

To investigate test case details:

  1. Select an item from the Total test cases column in either view.

The system displays test case details including:

  • Test case name

  • Average test run duration

  • Total test runs

  • Test failure rate

  • Test run activity link

Test cases link
Figure 4. Example test cases list with run activity link highlighted.

Analyze test run activity patterns

You can view detailed execution patterns for individual test cases to understand their behavior over time.

To analyze test run activity:

  1. Select Total test cases in either view.

  2. Select View run activity next to a test case.

The test run activity displays:

  • Workflow name

  • Test average run time

  • Number of total, successful, failed, and skipped runs.

Each bar on the graph represents a workflow run. Select a bar to display the:

  • Workflow run ID

  • Run date and time

  • Run duration

Below the graph is the run ID linking to the run details, and any test output.

Test run activity
Figure 5. Example of selecting a bar on the test run activity graph.

Monitor total runs performance

In the Test suites view, you can examine run-level performance details for test suites.

To monitor total runs performance:

  1. In the Test suites view, select an item from the Total runs column.

The system displays run details including:

  • Run time

  • Run ID: select to display run details in a new browser tab.

  • Run status

  • Total test cases

  • Number of failed test cases

Compare metrics

Use this feature to compare metrics among all organizations in the tenant. You can compare metrics within select charts in the analytics dashboards. In the generated list of all organizations, sort by the organization name or its status. Select an organization to drill down to the component level to display a more fine-grained status list. Hover over a status item to display more information.

You can only compare metrics for charts with Two arrows on the upper right.

To compare metrics:

  1. Select Analytics on the left pane, and then select a dashboard.

  2. Select any Two arrows on the upper right of a chart to display the list of organizations and their status.

    The number of items in the compare metrics list equals the total displayed in the chart.

  3. (Optional) Hover over a status to display more information.

  4. (Optional) Select Sort down or Sort up next to a column heading to sort on that heading.

  5. (Optional) Select an organization to list more information about each child organization and/or component within that organization.

  6. (Optional) Select a child organization to list more details about each child organization and/or component within that child organization.

The list of the status of all organizations and components for the specific metric is displayed.

Troubleshoot test insights issues

Address common issues when Test insights data is not appearing or appears incomplete in the dashboard.

Missing test result data

Test insights require test result data from workflow executions with proper result publishing.

Problem: Test insights display no test data

Solution: Confirm test result publishing actions are configured in workflows and that test executions generate supported result formats.

To resolve missing test result data:

  1. Review workflows that execute tests.

  2. Confirm test result publishing actions are configured:

    - name: Run tests
  run: npm test

- name: Publish test results
  uses: cloudbees-unify/publish-test-results@v1
  with:
    test-results: test-results.xml
    format: junit
    ▼

  3. Verify supported test result formats are used (JUnit XML, TestNG, NUnit).

  4. Check that test executions generate result files in expected locations.

Invalid test result formats

Test insights require test result data in specific supported formats.

To check test result formatting:

  1. Verify test executions complete successfully in workflow runs.

  2. Confirm test results appear in workflow run details after execution.

  3. Check that test result files are generated in the expected format and location.

  4. Ensure test result formats match supported specifications (JUnit XML, TestNG, NUnit).

Test insights dashboard populates with data from subsequent test executions that include proper result publishing.

Related pages

Track software delivery activity
Monitor CI insights