Analyze application module quality
Use the aggregated data from your application modules to analyze product quality across application modules.
Analyze an application module's quality
The Overview tab provides a set of widgets with which you can monitor quality aspects of application modules.
Use the default set of widgets, or select other widgets from the Widget Gallery. You can also design your own customized widgets. For more details, see Dashboard.
The scope of the widgets in the Overview tab is set by the by the application modules selected in the Application Modules tree.
The widgets aggregate data from all the features associated with the selected application modules in the tree.
Further filter the widget data using the Filter categories in the right pane.
Identify application modules affected by recent development
Even after you release your application, track quality while you continue development. ALM Octane helps you find application modules affected by recent activity.
Use the following tools to find application modules affected by recent work:
Tracking tool | Description |
---|---|
Dashboard widget: Commits by application module |
Shows how many changes committed in your SCM system during a certain time frame are associated with each application module. Note: To use this widget, you must assign user stories and defects to application modules. ALM Octane connects commits to application modules by reading the user story or defect name in a commit's message. |
Pipelines > Overview widget: Application Modules |
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, see Assign items to application modules. |
Application modules column in the pipeline runs Tests tab. | Add the column to the grid of Test Runs to see which application module is affected by each test run. You can filter for failed test runs if you want to see which application modules are associated with failing tests. See also Analyze test failures. |
See also: