Analyze product quality

After creating and assigning application quality, you need to evaluate the overall quality.

Tracking product quality

Tests and defects enable you to track product quality, usually after a release has gone out.

Tests created in the Backlog enable you to track release quality by testing features that are new to a specific release. These tests can also be assigned to application modules to evaluate product quality.

Automated tests, such as those discovered during a CI server's pipeline run, can also give you an idea of the quality of your build processes for the overall product.

To track product quality, we assign tests and defects to application modules and then use the dashboard to analyze the quality.

Tip: Make sure that all tests and defects are associated with an application module: in the Quality module, click the Unassigned link above the application modules tree. Then assign them accordingly to application modules.

Back to top

Transitioning from tracking release quality to tracking product quality

Tests you create to track release quality generally test features that are new to a specific release.

An example of a new feature for a specific release could be an improved shopping cart. In the Backlog release tree, you probably have a feature node dedicated specifically to the shopping cart.

Example:  

Feature: Shopping Cart
   User Story: Adding to cart
      Test: Adding one item to cart
      Test: Adding multiple items to cart
      Test: Adding from wish list to cart

When it is time to track overall product quality in the Quality module, you can run the same tests, but in the context of product functionality, such as overall navigation. This way, you can analyze the quality of the navigation capabilities of the user's experience when adding items to the shopping cart.

Example:  

Application module: Navigation
   Sub-application module: Adding to cart
      Test: Adding one item to cart
      Test: Adding multiple items to cart
      Test: Adding from wish list to cart

Because tests can belong to more than one application module, you could test the shopping cart in the context of other functional areas also.

Example:  

Application module: Navigation
   Sub-application module: Adding to cart
      Test: Adding one item to cart
      Test: Adding multiple items to cart
      Test: Adding from wish list to cart
Application module: Multiple selections
      Test: Adding multiple items to cart
      Test: Deleting multiple items from cart

Back to top

Analyze product quality in the Quality module

  1. In the Application Module tree in the Quality module, navigate to the relevant node in the tree. The graphs or charts that you view aggregate the data relevant to the selected node.

  2. Click Overview.

    You can change the set of widgets displayed:

    • Add a widget. Click + to open the widget gallery. Select a predefined widget or create a custom widget.

      Tip: To find widgets related to application modules, use the search box in the widget gallery.

      You can find additional application-module related widgets in ALM Octane's Dashboard module.

    • Remove a widget. Hover over the top right corner of the widget, and select Remove. This does not delete the widget from the widget gallery.

  3. Click a segment of a graph to see a summary preview of the items included the graph. You can click the link for the item to edit it. After saving, the results displayed in the widget in the Overview tab is updated.

For details on using widgets or creating a customized widget, see Use the ALM Octane Dashboard.

Identify application modules affected by recent development

Once your product's first release has gone out, you want to track the quality of your application modules as you continue developing.

ALM Octane helps you find application modules affected by recent activity.

  • Commits by application module dashboard widget.

    Shows how many of the changes committed in your SCM system during a certain time frame are associated with each application module.

    Note: To use this widget, user stories and defects must be assigned to application modules. The association of commits with application modules is made via the user story or defect mentioned in a commit's message.

  • Application Modules widget in the Pipelines module (pipeline overview and Failure Analysis tab in a pipeline run).

    Lists the application modules currently associated with automated tests that failed in this pipeline run. The widget shows how many of the tests assigned to the application module failed.

    Note: To use this widget, automated tests must be assigned to application modules. For details on assigning items to application modules, see Work with application modules.

  • Application modules column in a pipeline run's Failure Analysis tab.

    Add the column to the grid of failed test runs to see which application module is affected by each failure. See also Analyze automated test failures.

Next steps: