Test ManagementScript MappingDashboard tab
Dashboard tab
The Dashboard tab of the Script Mapping screen (/script-mapping?tab=dashboard) turns your mappings into reportable numbers. It is where Script Mapping opens.
What the tab shows
Section titled “What the tab shows”Four stat cards head the tab — Total Test Cases, Mapped (with coverage %), Unmapped, and Sync Health (synced mappings ÷ all mappings) — followed by a Sync Status Breakdown bar with a drill-down card per status, and a Quick Actions row.
The Sync Status Breakdown bar is split by status colour, with one card per status underneath:
Hover the info icon on a status card to see what that status means and what to do about it:
Click a status card to drill into the mappings in that state (click it again to close the list). The list is titled Synced Mappings, Scripts Changed on Disk, Missing Script Files or Test Cases Updated After Mapping, with an item count. Each row shows the test case, its priority, the script path, the test name, a short reason (for the three warning states) and when it was last synced:
Quick Actions
Section titled “Quick Actions”The Quick Actions row has three buttons:
| Button | What it does |
|---|---|
| Check Sync Status | Re-scans every mapping against the files on disk (see below). |
| View Mapped Test Cases | Switches to the Mapped Test Cases tab. |
| View Unmapped Test Cases | Switches to the Map Test Cases tab, where the unmapped cases are listed. |
Checking sync status
Section titled “Checking sync status”Mappings don’t re-validate themselves on every page load. Use Check Sync Status in the Dashboard’s Quick Actions to re-scan all mappings against the current state of the files on disk: a mapping whose script file no longer exists becomes Script Missing, one whose file content changed since it was last synced becomes Script Updated, and a mapping checked for the first time (or whose missing file is back) is marked Synced. A check never clears an existing Case Updated or Script Updated warning; those stay until someone re-syncs the mapping (Re-sync or Mark Synced on the Mapped Test Cases tab). A “Sync check completed” toast confirms the run. Run it after a code change, a refactor, or whenever the health numbers look out of date.
Related
Section titled “Related”- Script Mapping overview — the screen and its tabs.
- Mapped Test Cases tab — manage existing links.
- Map Test Cases tab — create new links.
- Coverage — the wider coverage picture.