Close popover

Table of Contents

Changing application quality metrics settings

Version:

The Application Quality settings provides configurable options related to quality metrics. You can change the default settings for metrics displayed to meet your business needs.

To change settings on the landing page and to enable the EnableBuiltOnAppSelectionForQuality toggle that allow you to select which built-on applications are included, your operator ID must have the SysAdm4 privilege.

On the Application Quality settings landing page, you can modify the following settings:

  • Application(s) included – If you want the test coverage report to include only rules from the current application, select Current application only. If you want the test coverage report to also include rules from built-on applications, select Include built-on applications. By default, only current application is selected. If you enable the EnableBuiltOnAppSelectionForQuality toggle, you can select which built-on application will be included.
    If a master user starts an application-level coverage session for an application, then that user's configuration of this setting is in effect for all users that execute test coverage for the duration of this session.
  • Ignore test rulesets when calculating Guardrail score – When you enable this setting, Guardrail score is calculated without taking test rulesets into account. This is the default behavior. When you disable this setting, test rulesets are taken into account when calculating Guardrail score.
  • Quality trends – Use this setting to change the date range of the trend graphs on the Application Quality, Application: Test coverage and Application: Unit testing landing pages. The default value is Last 2 weeks.
  • Test case execution – Use this setting to change the number of days, from the time that they are executed that tests are treated as executed by the Application Quality dashboard and coverage reports. By default, a test executed later than seven days ago is considered too old to be included on the Application Quality dashboard and in reports.
  • Scenario test case execution – Use this setting to add a delay (in milliseconds) to the execution of steps in a scenario test.

  • Improving your compliance score

    Follow development best practices to improve your compliance score. By eliminating risks, such as custom code or degraded performance, you can improve quality and resolve issues before your application goes into production.

  • Viewing application quality metrics

    Quickly identify areas within your application that need improvement by viewing metrics related to your application's health on the Application Quality dashboard.

  • Estimating test coverage

    View historical test coverage metrics and generate reports containing the number of executable rules and their test coverage. Use the data to analyze changes in test coverage, and to verify which rules require testing.

  • Application quality metrics

    The Application Quality dashboard displays metrics for guardrails, test coverage, and unit testing that you can use to assess the overall health of your application and identify areas that require improvement. You can change the default ranges for the color codes by modifying the corresponding when rules in the Data-Application-Quality class.

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.