1. Docs
  2. Build tests
  3. InSight

InSight

InSight is the first item in the main menu and the page you land on after login. Its Execution tab tells you how your runs went; its Test Health tab tells you how much of your application your tests really prove.

7 min read Updated CustomersAdmins

In short

On this page you can

  • See success rate, runs, failed runs, flaky test cases, run time and time saved for a period.
  • Find the failures that share one cause, and the slowest and least stable test cases.
  • Measure coverage in four pillars and one automation maturity score.
  • Get the next three things to fix, each with a ready MCP prompt.
  • Download Excel or PDF, and save Test Health snapshots.

How to use it

  1. Open InSight; pick the Execution or Test Health tab.
  2. On Execution, choose the Period and read the six summary cards.
  3. Go down to Failure clusters and Flaky scenarios, and open the worst one.
  4. On Test Health, read the pillars, then work through Fix these first.
  5. Click Save report before a release to keep the picture.

At a glance

Where
Main menu › InSight, the first item. It is also the page you see after login. Tabs: Execution, Test Health.
Who
Everyone with access to the project. Admin and User see exactly the same numbers.
You need
Execution: runs in the chosen period. Test Health: requirements from Analyze, test cases and pipelines.
Time
Numbers are calculated when you open the tab or click Refresh, in a few seconds.
Produces
Excel and PDF downloads, saved Test Health reports, ready prompts for AI assistants.
Reads from
Run reports, requirements, test cases, pipelines and schedules, actions, tasks, agents and AI agent runs.
Project types
The same for WEB, MOBILE and DESKTOP. Load tests count as runs in Execution and are left out of Test Health’s scenario funnel.

Start from your question#

Where InSight fits#

The main menu is the order of work. InSight sits above it and reads every step: Test Health measures how far Discover, Analyze, Automate and Schedule have got, and Execution measures what Schedule’s runs produced in Report.

  1. 1DiscoverActions used by tests
  2. 2AnalyzeRequirements to prove
  3. 3AutomateScenarios that check results
  4. 4SchedulePipelines and timers
  5. 5ReportRun results
  6. 6MaintenanceRepairs to review

Use Report for one run. Use InSight for the pattern across runs and for the state of the whole project.

Why use it#

  • One answer to “are we green?” The success rate, failed runs and the pipeline run strip show it per period and per pipeline.
  • Fix causes, not symptoms. Failure clusters group failed steps with the same error, so twelve red test cases can turn out to be one broken login.
  • Find the tests nobody trusts. Flaky scores and the trust checks find test cases that flip, or pass without checking anything.
  • Coverage you can defend. A requirement only counts as covered when a scenario that checks a result passed on its last run.
  • Work for you or your AI assistant. Every recommendation has a Copy MCP prompt button with the task already written.

The building blocks#

Scenario
InSight’s word for a test case. Templates and test cases tagged planned are not counted as real scenarios in Test Health.
Run
One pipeline run, or one test case run started on its own. A pipeline run with ten test cases is one run.
Scenario run
One execution of one test case inside a run. The success rate is counted over these.
Sub-requirement
One behaviour from Analyze that needs a test. Test Health counts coverage over sub-requirements.
Proving scenario
A scenario with at least one step that checks a result (assertion, visibility check with text, validation-mode AI step, API extractor, assert-text step, load test), directly or in a template it calls.
Pillar
One of four coverage percentages: requirement, scenario, risk and action coverage.
Maturity
A weighted average of the four pillars, 0–100.
Failure cluster
Failed steps whose error messages are the same once numbers and quoted values are ignored.
Flaky score
How often a scenario’s result flips between runs: 0 stable, 1 flips every time.
Period
The date range of the Execution tab. Each number is compared with the period of the same length just before it.

The screen#

InSight Execution tab on the sample project: tab row with Period, Live chip, Refresh and Download; Run environment row; six summary cards
InSight with the Execution tab open.

The tab row stays at the top while the content scrolls. Its right side holds the tools of the open tab.

TabAnswersTools in the tab row
ExecutionHow did our runs go in this period? What failed, why, what is flaky or slow?Period picker, live chip, Refresh, Download (Excel or PDF)
Test HealthHow much of the application do our tests prove, and what should we fix first?Live chip, Refresh, Save report, Reports, PDF
  • Live chip. Live · just now or Live · {n} min ago: how old the numbers are. They do not update by themselves; click Refresh.
  • Which tab opens. The one in the address (?tab=execution or ?tab=health), otherwise the last one you used in this browser, otherwise Execution. A project with AI agents opens on Test Health the first time.
  • Auto-heal reviews. When repairs wait for review, a line says “{n} auto-heal repair(s) on {m} test case(s) wait for review.” with Review, which opens Maintain › Auto-heal. It sits in the Run environment row on Execution and at the top of Fix these first on Test Health.
Video transcript

InSight opens on Execution: what ran in the selected period, and how it went. The period sets the window for every number on the page. Six cards sum it up: success rate, runs, failed runs, flaky scenarios, average run time and time saved. The pipeline run strip shows the last 14 runs of each pipeline. A row of red is where to look. Failure clusters group failed steps that broke for the same reason. Test Health asks a different question: how much of the product is really proven? Automation maturity is one score built from four pillars, each with an 80% target. Fix these first lists the three actions that raise the score most. The coverage funnel shows where requirements drop out on the way to a passing test. Modules × coverage ranks every module by risk, coverage and last results.

Execution’s period, cards and clusters, then Test Health’s pillars, Fix these first and a saved report.

Before you start#

To seeYou needWhere you get it
Execution numbersPipeline runs, or test cases run on their own, in the period. Dry runs are not counted.Schedule; Quick Start, step 6
Requirement and risk coverageMain requirements with sub-requirements, linked scenarios, severitiesAnalyze
Scenario coverage, pipeline maturityScenarios in pipelines that have run; schedulesAutomate and Schedule
Action coverageActions used by test stepsDiscover › Actions
Agents online, stuck runsAgents installed for the companyInstall an agent

Other ways to see the same picture#

WayBest whenYou get
InSightYou want the whole project at a glanceExecution and Test Health, live
ReportYou need the details of one runSteps, screenshots, logs, AI verdicts
Discover › Setup RoadmapYou are still setting the project upThe next setup step, see Progress meters
Excel / PDF downloadA status meeting or an auditOne sheet per Execution section, or a print of the tab
AI assistant through MCPYou work from your IDE or chatThe Test Health numbers and the open work as a list. See MCP.

Best practices#

Do

Don’t

  • Read the success rate without the number of runs next to it.
  • Count “Passed” as proof: a scenario that checks nothing passes too.
  • Leave runs stuck in Running; they distort run time and the strip.
  • Chase a maturity score by adding scenarios that do not check results.
  • Expect InSight to refresh itself; click Refresh after a run.

In this section#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai
© 2026 Selenity Technology · SmartestQAsmartestqa.aiThis page as MarkdownChecked against smarttest-fe predev 2a8c79cc (pages/dashboard/Dashboard.js, dashboardTabs.js, execution/*, test-health/*, menu-items/dashboard.js, routes/MainRoutes.js), smarttest-be 633c2a03 (quality/ExecutionHealthService, QualityHealthService, QualityRules, QualityHealthController)