Track and analyze build, release, and product quality

ALM Octane contains all the information that you need to analyze your product development progress and quality.

Use ALM Octane's various dashboards, overview widgets, and grids to track and analyze various types of information:

  • Track the progress of your backlog development.

  • Track test run results on application modules to determine your product quality.

  • Track test run results on backlog items to determine your release quality.

  • Follow your tests' coverage of various testing environments.

In the Pipelines module, you can open a pipeline to see all of its runs, dating back to when the pipeline was added to ALM Octane. When you open a specific run, you can learn more:

  • Gain insight into build quality by analyzing failed automated tests.

  • Track changes committed by your developers and testers, and their affect on build stability.

Analyze overall quality in the Dashboard

ALM Octane's dashboard comes with many useful charts and graphs for analyzing release and product quality. You can also design your own by configuring widgets.

  1. Open the Dashboard module.

  2. Click to select the layout you prefer.

  3. Organize graphs relevant to you on the dashboard:

    Click + to add a widget to the dashboard. You can select widgets from ALM Octane's widget gallery, or click Add custom graph to design your own. For details, see Add widgets.

  4. In each widget, click the menu in the top-right corner to access the following actions: 

    Reload, Full screen, Export report, Configure, Remove.

    Select Configure to customize the content and filtering for the specific chart or graph.

  5. On the widgets, click an area in a chart or graph to view more detailed information.

Back to top

View an overview of your product or release quality

  1. In the Quality module or the Backlog module, select the Overview tab.

  2. Add widgets, customize them, or design your own, as you would on the Dashboard. For details, see Use the ALM Octane Dashboard.

  3. Include or exclude various types of information from the graph:
    1. Use the filter panel on the right to include or exclude, for example, environment details, releases, and tags.

      Or

      Define additional widget filters in the widget configurations. For details, see Use the ALM Octane Dashboard.

    2. View widget filter icons and tooltips to see if and how the results have been filtered without having to expand the right pane and without having to look at widget configurations. When filters have been defined in widget configurations, the filter icon is marked orange.

  4. Hover over or click various areas of a chart or graph to view more detailed information.

The various widgets display information for the application module or backlog item that you select in the tree.

For details, see Analyze release progress and quality and Analyze product quality.

Back to top

Analyze product and release quality in ALM Octane grids

After you run tests from ALM Octane, the test run results are displayed in the various grids: Quality > Tests, Backlog > Tests / Features / Stories

The results are aggregated and filtered according to the tags you select in the filter, the items you select in the tree, and so on.

Back to top

Analyze build quality using pipeline data

In the Pipelines module, open the Pipelines tab and select a pipeline.

Open a specific pipeline run:

  • To open the last or current run, click the number to the right of the pipeline name.

  • To open a previous run, click the pipeline's ID to open the pipeline. In the Runs tab, click the ID of a specific run.

Here are some of the things you can see within a pipeline run:

  • If a pipeline run includes failed automated tests, use the Failure Analysis tab to learn more. For details, see Analyze automated test failures.

  • If you add tags to your pipeline runs, you can use the Pipeline runs by user tag dashboard widget to view your pipeline runs, divided according to your tags.

    Example:  

    1. Create tags that describe different reasons for build failure. For example,

      • Database problem

      • Broken build

      • Out of memory

      • Merge issues

    2. In the dashboard, add the Pipeline runs by user tag widget to your dashboard.

    3. The widget shows you how many of your pipeline runs are failing for each reason you listed.

    You can also build your own dashboard widgets to display pipeline runs. Create a custom widget, and in Scope > Item type, select Pipeline runs.

  • If your Jenkins or Bamboo server is set up to work with an SCM system, view commits and stories associated with each pipeline run. For details, see Track changes committed to your Source Control Management system.

Back to top