Studio

Studio · Quality management

Quality metrics

In Quality › Metrics, choose a test type and time range to inspect results and trends. The overview also shows recent dimension results.

Metrics distinguish recorded results from unverified items
Metrics distinguish recorded results from unverified items

Metric definitions

DataSource
Task, scenario, and checkpoint outcomesExplicit findings and evidence submitted by each dimension
Automated passes, failures, skips, and durationUploaded reports from Vitest, Playwright, and other test runners
Dependency vulnerabilitiesDependency audit output, separated into production and development dependencies
Page and API performanceCompare measurements for the same page or endpoint
Permission checksCompare expected and observed access by role and action. Check which cases lack evidence
Scan findingsInspect results submitted in SARIF format and the affected locations
Code qualityFindings and locations recorded in the code quality report
Follow-up tasksLinked defects, questions, test cases, scenarios, and cleanup tasks

Missing reports produce no corresponding metrics. An empty value does not mean zero problems. Unverified and not applicable do not mean passed.

Open a metric to inspect the related tests, scenarios, or findings. Before comparing results, check the type, scope, code commit, and selected dimensions.

Adding or removing scenarios changes totals. Stable scenario keys support comparisons across tests. More tests or fewer issues only become meaningful alongside scope changes. Use reports and evidence to understand the difference.

NocoBase docs assistant

Ask anything about NocoBase…

Each question is answered independently, without earlier questions or answers. Include all relevant context.