---
title: "How the numbers work"
section: "Deploys & Repos"
description: "How SmartestQA Deploys & Repos calculates Tested after deploy, Running untested, each cell’s test state, the untested streak, commit counts and “3 h ago”."
url: https://docs.smartestqa.ai/en/deployments-numbers.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "tested after deploy formula running untested deploys in last 7 days connected repositories tested window not tested streak commits files time ago short sha"
---
# Deploys & Repos: How the numbers work

Every number and state on the Deploys & Repos page, how it is calculated, and an example you can check against your own project.

## In short

**On this page you can**

- Understand which pipeline runs count as testing a deploy.
- Read Tested after deploy and Running untested correctly.
- Know why one green run after a red one makes a deploy Tested .
- See why a custom environment lowers the tested ratio.

**How to use it**

1. Find the deploy’s time and the next successful deploy to the same environment.
2. List the pipeline runs in that environment between the two times.
3. Take the newest run: running, broken or passed decides the chip.
4. Compare with the KPI cards, which count the last 7 days.

## Tested after: which runs count

**The tested-after window** — Shown in: cell chips, Tested after column, Tests after deploy

```text
window   = from this deploy's time
           until the next SUCCESSFUL deploy of the same repository to the same environment (open if none)
runs     = pipeline runs of the project in the same environment (DEV, TEST or PRP)
           that started inside the window           listed: newest 10
per run  : total   = test case results in the run
           passed  = results Success or Completed
           failed  = results Failed or Error
           running = results Running or New
state    = newest run has running > 0   → Test running
           newest run has failed > 0    → n broken · passed/total
           otherwise                    → Tested · passed/total
           no run in the window         → Not tested
           environment not DEV/TEST/PRP → No pipeline environment
```

**Example:** `web` v2.14 reaches TEST at 10:00. The next TEST deploy of `web` is at 15:00.

| Pipeline run (TEST) | Start | Result | In the window? |
| --- | --- | --- | --- |
| Nightly regression | 09:55 | 40/40 | No: before the deploy, it belongs to the previous version |
| Smoke | 10:05 | 18/20, 2 failed | Yes |
| Smoke (after a fix in the test) | 12:00 | 20/20 | Yes, newest |
| Smoke | 15:10 | 20/20 | No: belongs to the 15:00 deploy |

The newest run in the window (12:00) decides: Tested · 20/20. Both runs are listed under [**Tests after deploy**](https://docs.smartestqa.ai/en/deployments-overview.html#deploy-detail). A deploy that was broken first and then passed counts as tested.

**Only [pipeline](https://docs.smartestqa.ai/en/schedule-create.html) runs count.** [Dry runs](https://docs.smartestqa.ai/en/automate-dry-run.html) in Automate have no pipeline environment and are not matched. The match is by environment for the whole project: any pipeline in TEST tests every service deployed to TEST at that time. A failed or cancelled deploy has no window of its own; runs after it still belong to the last successful deploy.

## Cell states

**What a cell in Currently running versions shows** — Shown in: Overview › Currently running versions

```text
records  = the newest 20 deploy records of this repository in this environment
current  = the newest SUCCEEDED record among them       → commit, version, age, test chip
pending  = the newest record, if it is not "current"    → "Deploy in progress" (status In progress)
                                                           "Last deploy failed · sha" (any other status)
empty    = no record: "No deploy yet" if the environment is switched on in the mapping, else "Not mapped"
```

| Chip | Colour | From |
| --- | --- | --- |
| **Tested** · *p/t* | Green | State Tested, newest run’s passed and total |
| *f* **broken** · *p/t* | Red | State broken, newest run’s failed, passed and total |
| **Test running** · *[pipeline](https://docs.smartestqa.ai/en/schedule-create.html)* | Blue | State running, newest run’s pipeline name |
| **Not tested** (· *n* **deploys**) | Amber | No run in the window; streak below |
| [**No pipeline environment**](https://docs.smartestqa.ai/en/deployments-troubleshooting.html#fix-no-pipeline-env) | Grey | An environment pipelines do not use |

**Example:** TEST received `a1b2c3d` (Succeeded) at 10:00 and `c4d5e6f` (Failed) at 11:00. The cell shows `a1b2c3d` with its test chip, and below it “Last deploy failed · c4d5e6f”, because `a1b2c3d` is what still runs. A cancelled deploy also shows “Last deploy failed”.

## Untested streak

**“Not tested · n deploys”** — Shown in: Currently running versions

```text
n = number of the most recent SUCCESSFUL deploys, in a row, whose state is Not tested
    (looks at the newest 5 successful deploys and stops at the first one that is not Not tested)
label = "Not tested"              when n = 1
        "Not tested · n deploys"  when n > 1
```

**Example:** `api` in TEST: Monday’s deploy was tested; Tuesday’s, Wednesday’s and Thursday’s deploys had no [pipeline](https://docs.smartestqa.ai/en/schedule-create.html) run before the next deploy. n = 3: the cell reads Not tested · 3 deploys. Three versions went through TEST without a test. One pipeline run now makes Thursday’s deploy tested and the chip changes to its result.

## The KPI cards

**The four cards at the top** — Shown in: Deploys & Repos, above the tabs

```text
Connected repositories = repositories of this project (deleted ones not counted)
Deploys in last 7 days = SUCCESSFUL deploys of the project in the last 7 × 24 hours
Tested after deploy    = tested ÷ Deploys in last 7 days, shown as "tested / deploys"
                         tested = those deploys whose state is Tested, broken or Test running
                         (Not tested and No pipeline environment do not count)
Running untested       = number of cells (repository × environment) whose current version is Not tested
                         amber when > 0
```

**Example:** two repositories, `web` and `api`. Successful deploys in the last 7 days:

| Repository · environment | Deploys | Tested | Current version |
| --- | --- | --- | --- |
| web · TEST | 3 | 2 | Not tested (the newest one) |
| web · PRP | 1 | 1 | Tested |
| api · TEST | 2 | 2 | 1 broken |
| api · STAGING | 1 | 0 | No [pipeline](https://docs.smartestqa.ai/en/schedule-create.html) environment |

Cards: Connected repositories 2 · Deploys in last 7 days 7 · Tested after deploy 5 / 7 · Running untested 1 (only web · TEST). The broken api deploy counts as tested: a pipeline did run against it. The STAGING deploy is in the 7 but can never be tested, so custom environments lower the ratio.

## Commits and files

**“← 9f8e7d6 · 5 commits”, “5 commits · 12 files”** — Shown in: Deploy history, Deploy detail

```text
previous version = the newest SUCCESSFUL deploy of the same repository to the same environment
                   before this one
commits          = commits after the previous version up to and including this one (from your Git provider)
files            = files changed between the two versions
same commit      → 0 commits, 0 files (a redeploy)
lists shown      : up to 100 commits and 300 files; the counts can be higher
```

**Example:** PRP ran `9f8e7d6`. CI deploys `a1b2c3d` to PRP; on the branch there are 5 commits between them touching 12 files. History shows `a1b2c3d ← 9f8e7d6 · 5 commits`; the detail shows 5 commits · 12 files. Line counts (`+18 −4`) appear for GitHub, Gitea and Bitbucket; GitLab and Azure DevOps give the file status only.

Counts need an access token. Without one the history shows only `← 9f8e7d6`, except for a redeploy, which always shows 0 commits.

## Relative times and short commits

**“just now”, “12 min ago”, “3 h ago”, “2 d ago”** — Shown in: cells, Last deploy column

```text
s = seconds since the deploy (or the last notification, in Last deploy)
s < 60                       → just now
m = round(s ÷ 60);  m < 60    → m min ago
h = round(m ÷ 60);  h < 24    → h h ago
otherwise                    → round(h ÷ 24) d ago
short commit = the first 7 characters of the commit SHA
```

| Time since | Calculation | Shown |
| --- | --- | --- |
| 45 s | s < 60 | just now |
| 89 s | round(1.48) = 1 | 1 min ago |
| 90 min | round(1.5) = 2 | 2 h ago |
| 23 h 40 min | round(23.67) = 24, not < 24 | 1 d ago |
| 36 h | round(1.5) = 2 | 2 d ago |

The page does not refresh the ages by itself; click [Refresh](https://docs.smartestqa.ai/en/deployments-overview.html#refresh). When CI sends no `deployedAt`, the deploy time is the moment the notification arrived.
