Track and analyze product quality

This topic discusses how to associate tests with product areas, and track the product areas quality.

Transition from release to product quality

When you first create tests, you usually create tests of a specific feature assigned to a release.

For example, you have a feature to improve the shopping cart area of the application . In the backlog release tree, there is a feature node for the shopping cart. The feature contains user stories. Each user story has acceptance tests.

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

To track product quality, use the same tests. Group them in the context of an application module, such as product navigation:

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

You can also use the tests for other functional areas:

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

In doing this, you change from testing release quality to testing product quality.

Back to top

Analyze product quality

To analyze product quality, ensure that you associate features, user stories, defects, and tests with application modules.

ALM Octane uses the test results and defect analysis to paint a picture of application health across releases. Using these measures, you gain a global picture of your application's quality at a specified point.

You can analyze product quality from one of the following areas:

Area Details
Quality module Features and Tests tabs

Add more grid columns including:

  • Risky commit count (Features tab)

  • Last runs (Tests tab)

    The Last runs grid summarizes the last unique native run statuses for each test. If you run a test with the same configuration as a previous test run, ALM Octane updates the new result. For details, see Last runs.

Quality module Overview tab

View test run results by adding different widgets from the Overview tab, such as:

To see information for a specific application module, select the node in the Quality module's Application Modules tree.

Back to top

See also: