Skip to content

Using the missing metrics metric

Jump to bottom
Sebastiaan Koot edited this page Nov 6, 2025 · 2 revisions

The missing metrics metric can be very useful as it provides insights in the capabilities of Quality-time that are not utilised in the current report.

This metric can be used to notify the user if there are metrics in your report/subject, that could be added to provide more valuable insights.

To do this properly, the user should tell Quality-time, by configuring the source of the missing metrics metric, what stack is being used in this project.

Before configuring this metric, the development team should run through the below list to identify which sources are being used in the stack of this software development project.

Setting the source filter

After identifying the sources available for this software development project, the source filter can be configured for the missing metrics metrics so that it will provide more accurate alerts. !

List of possible sources Quality-time can connect to

Java stack sources

Python stack sources

Rust stack sources

PHP stack sources

.NET stack sources

Javascript stack sources

Security scanning tools

Pipeline, CI, repository sources and project tracking boards

Performance testing tools

Accessibility scanning tools

Testing frameworks and tools

Code quality scanning tools

The official documentation describes how to deploy, develop and configure Quality-time.

Clone this wiki locally