Share this page

# Analyze product quality

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

In this topic:

## 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.

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:

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:

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.

The test results and defect analysis are used to show 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: Features tab > Risky commit count Tests tab > Last runs 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, the new result is updated. For details, see Plan and run manual tests.
Quality module > Overview tab | View test run results by adding different widgets from the Overview tab, such as: Open defects by application module Last run status by application module Last run status by browser Quality by application module To see information for a specific application module, select the node in the Quality module's Application Modules tree.

Back to top

See also:

- Issues
- Application module quality
- Release quality

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.1 All View Local Help Center View Online Help Center Version: