1. Docs
  2. Build tests
  3. Discover
  4. How the numbers work

How the numbers work

Every number and colour in Discover, how it is calculated, and an example you can check against your own project.

3 min read Updated CustomersAdmins

In short

On this page you can

  • Read the locator chip: main locator, fallbacks and the Strong, Medium, Fragile tiers.
  • Understand what the Cases badge counts and what it leaves out.
  • Calculate the Describe the app roadmap percentage from pages and purposes.
  • Work out a page’s Tested coverage from tasks, validations and transitions.
  • Decode the status icon, page pill counts and the “n unreachable” chip.

How to use it

  1. Find the section for the number or colour you see on screen.
  2. Read its formula, then follow the worked example.
  3. Recalculate it with the values from your own project.
  4. Act on the result: add an id locator, write purposes, or add tests.

Locator chip#

Shown in: Action List › Locator column
main locator  = the locator with the highest confidence score (else the first one)
"+n"          = number of locators − 1  (the fallbacks)
colour        = by the main locator's TYPE (key), not by its value
red           = any locator FAILED in its last run
dot           = green / red when a last-run status exists
TierLocator typesMeaning
Strongaccessibility_id, resource-id, id, nameIdentity based; least affected by UI changes.
Mediumcss, linktext, any other typeModerately robust.
Fragilexpath, class, tagBreaks when the page structure changes.

Read it right: the web recorder stores its locators as XPath, and the mobile resource-id locator is also stored as an XPath. So recorded actions usually show XPath in amber even though the recorder already rejected dynamic and non-unique locators. Judge a recorded action by its last-run status and the confidence in its detail rows; add an id or name locator by hand where one exists.

In the action’s detail rows, a locator with a last run shows its confidence: ≥ 80% green, ≥ 50% amber, below 50% red.

Cases badge#

Shown in: Action List › Cases column
Cases = number of distinct test cases with a step that uses this action directly
"-"   = 0      blue = more than 5

Example: Click Sign In is a step in 12 test cases and in one template that 30 other tests call. The badge shows 12: tests that reach the action only through a template are not counted. Click the badge for the Used Test Cases list. Sorting by Cases sorts across all result pages.

Setup Roadmap · Describe the app#

Shown in: Setup Roadmap tab
pages      = number of App Map pages
described  = pages whose Purpose is not empty
status     = TODO if pages = 0 · DONE if described ≥ 60% of pages · else PARTIAL
percent    = 40% + 60% × min(1, described ÷ (0.6 × pages))      shown as at most 99% until DONE
next step unlocks at 90%
PagesDescribedCalculationShown
10040 + 60 × 040%
10340 + 60 × 3/670%
10540 + 60 × 5/690% · next step unlocked
1066 ≥ 60% of 10Done
251240 + 60 × 12/1588%

The roadmap tells you what to do: with no pages, “No pages yet. Click Discover Your App…”; with pages but missing purposes, “n pages have no purpose written. In App Map, select the page and write a sentence or two in Purpose”.

App Map · Tested#

Shown in: App Map list and map view
test points = tasks on the page
            + validation actions (Visibility Check, or Get named like "error", "invalid", "required"…)
            + transitions leaving the page
covered     = a point whose proof action is used by any test step (templates included)
coverage    = covered ÷ test points
map colour  = ≥ 80% green · 40–79% amber · < 40% red      "—" when the page has no tasks

Example: checkout has 3 tasks, 2 validation actions and 2 transitions: 7 points. Tests use the proof actions of 5 of them: 5 ÷ 7 = 71%, amber. Adding a test for “apply voucher” and one for the “invalid card” message brings it to 100%.

Test cases that use a task or validation action of the page count as that page’s tests; tests that only pass through it count as “pass through”. Red runs are failed, error or disconnected results; never run means no run status and no trace in logs or schedules.

Other indicators#

IndicatorHow it is decided
Status icon before the IDThe action’s last run: Success, Failed, Running, Skipped, Passed with warnings, Disconnected. Set only by test runs, never by edits.
Page pill countNumber of actions on that page (the active pill shows the current result total).
Module option Name (n)Number of pages in the module.
“n unreachable”Visible pages that no action leads to, shown only when there are 2 or more.

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

info@smartestqa.ai