Metrics for verifying application quality
The Application Quality landing page is essential to a lead system architect's (LSA) role as the rest of Dev Studio. It is one thing to implement functionality as per requirements, and another thing is to prove that the functionality works correctly and meets established quality standards. It is necessary to monitor how application quality trends – has it improved or gotten worse over time? Application Quality affects the rate at which the application moves through a Dev Ops pipeline. It also affects the rate at which new features can be added to the application.
The Application Quality settings provide configurable options related to quality metrics. You can change the default settings for metrics displayed to meet your business needs.
Settings
Establishing standard practices for your development team can prevent these types of issues and allows you to focus on delivering new features to your users. These practices include:
| Setting | Description | Effect |
|---|---|---|
| Applications Included | Current Application or Include Built-On Applications | If Include Built-On Applications is selected, the user is then allowed to select which Built-On applications to include |
| Guardrails | Ignore test rulesets when calculating Guardrails score? Defaulted to true | When true, exclude from the Guardrail score unit test setup activities and transforms placed within test rulesets |
| Quality trend interval | Two weeks to 6 months | Defines the Quality trend interval period |
| Test execution look-back duration | One week to 6 months | Defines the Test execution look-back duration period |
| Scenario test case execution | Configure delay for scenario test execution? Defaulted to false | Enable or Disables a scenario test case execution delay |
For more details on how to change application quality metrics settings, see Application quality metrics settings.
Rule coverage testing
The Application Quality landing page displays metrics for guardrails, test coverage, and unit testing that you can use to assess your application's overall health and identify areas that require improvement.
To open the Application Quality landing page, from the header of Dev Studio, click Configure > Application > Quality > Dashboard.
On the Test Coverage landing page, view a chart displaying test coverage metrics and generate specific user-level, application-level, and merged coverage reports. User-level reports contain the results of a single test coverage session that a user performs. In contrast, application-level reports contain results from multiple test coverage sessions that many users run. Merged reports contain results from multiple most recent application-level reports.
User-level: Single user in a single session. Different users can simultaneously perform their own user-level tests.
Application-level: Multi-session. The tab contains a Start new session button.
Use cases:
- A team is building or modifying an application and works on a sample application that is built on top of the actual application and maintains test artifacts in the test application. The team wants to generate a test coverage report of the actual application by running the test application tests or Current Application or Include Built-On Applications.
- The team wants to generate a test coverage report as part of the automated tests run in the CI/CD pipeline and use it for quality-gating purposes.
| Coverage and Unit Test Rules | Coverage-only Rules |
|---|---|
| Activities Case types Collections Data pages Data transforms Decision tables Decision trees Declare expressions Flows Map values Report definitions Strategies When |
Correspondence Declare Expression Flow action Section Validate Decision Data XML Stream HTML HTML Fragment Harness Paragraph |
For more details, refer to our Community article on Estimating test coverage.
This Topic is available in the following Module:
Want to help us improve this content?