Understanding Analytics

Overview

Analytics helps you see how API tests behave over time: stability, performance, failures, and coverage. In Shift Left Studio, Analytics is split into two surfaces:

Open Analytics from the main top navigation (Analytics is highlighted when you are in this module).

When to use which tab

• Use Dashboards when you want a role-specific lens (for example engineering leadership vs QA) and optional filters such as time range and focus project (including All projects).
• Use Project Analytics when you need project-scoped health: totals, success rate, coverage, execution summary, and expandable sections for trends and failures.

Questions Analytics can answer

• Are pass rates and response times trending in the right direction?
• Which endpoints are slowest or fail most often?
• How does one project compare across environments?
• Where should the team prioritize fixes before release?

Who uses Analytics

• QA / Testers — failure patterns, flaky signals, execution queues.
• Developers — endpoint health, regressions, latency.
• Leads — delivery, quality trends, release readiness (via persona dashboards).

Best practices

• Prefer trends over single-run spikes unless you are debugging a specific run (use Test reporting for run-level drill-down).
• Align time range and project filters with the question you are asking.
• Use Project Analytics accordions (trends, top failing tests, environment comparison) after scanning the overview cards.

Related articles

• Analytics dashboards
• Project analytics
• Test reporting
• Test execution