Analytics

What is this?

The analytics page shows metrics and trends for a selectable range (30/90/180/365 days) — unlike the dashboard, which shows the current status and what needs action right now.

How to use it

• Lab/Project: The toggle below the KPI tiles picks the scope. "Lab" (default) shows every metric organization-wide; "Project" narrows them down to a single project chosen from the dropdown — useful for measuring a project's performance instead of the whole organization's. The selection lives in the URL (?projectId=…) and survives changing the range or the analysis.
• Range: The four buttons in the top right select the analysis range. All metrics and charts refer to this range (and, if active, the selected project).
• KPI tiles: Completed tests, pass rate, avg. test duration, open test cases (with overdue count), and active testers (distinct people with a recorded execution in the range) — each with a trend arrow versus the equally long previous period, where meaningful. They always stay visible, regardless of which analysis is selected below.
• Choosing an analysis: The dropdown below the KPI tiles always shows only one of the following analyses at a time, not all of them stacked. The selection lives in the URL (?view=…) and survives a reload.
• Test throughput per week: Passed/failed tests per week.
• Failures by test case group: Where most failures happened in the range.
• Station utilization: Busy time per test station in the range.
• Recurring failures: The test case definitions that failed most often in the selected range — a plain frequency count as a starting point for spotting recurring problems. Clicking an entry opens the test case definition.
• Workload by assignee: Open test cases per person, weighted by estimated duration — independent of the range filter, because open work has no completion date to fall inside a window.
• Estimate accuracy: Actual duration versus estimate per test case group.
• Project progress: Progress bars for each active project with test cases.
• Export: The button at the top downloads all metrics and tables on this page as a file for the selected range.

Common issues

• "Active testers shows 0 even though tests were run." It counts whoever recorded an execution (performedAt) within the selected range — with a very short range this can be empty even if there was activity overall.
• "Workload by assignee doesn't change with the range filter." Intentional: open work has no completion date that could fall into a time window — the metric always shows the current state.