Skip to content

Mapped Test Cases tab

The Mapped Test Cases tab of the Script Mapping screen (/script-mapping?tab=mapped) lists every manual test case that already has automation linked to it, and lets you manage those links.

Each row shows the test case, the script path it maps to, the test name, the framework, and the mapping’s sync status. Row actions let you unlink the mapping, re-sync it, or open the automation.

The Mapped Test Cases tab

Once mapped, every manual case carries a precise pointer to the code that verifies it: the script path, the test name, and the framework. On the Mapped Test Cases tab, the View Script (new tab) action opens that test in the Test Explorer in a new browser tab — where you get the source, its run history, its results, and the option to run it, rather than just a read-only snippet. Your place in Script Mapping is kept in the original tab.

Each mapping reports one of four sync statuses. Testver rolls these up into the Sync Health headline and a stacked breakdown bar on the Dashboard, so a single glance tells you how much of your automation map is currently trustworthy.

Sync statusColourMeaning / action
SyncedGreenTest case and script file are in step. No action needed.
Script UpdatedAmberThe script file was modified on disk after mapping. Review the case to confirm it still matches the script.
Script MissingRedThe mapped script file was deleted or moved. Re-map the case to a valid file.
Case UpdatedBlueThe manual case was edited after mapping. The script may need updating to reflect the change.
Not MappedGreyNo mapping exists yet (shown for cases without a link).

From the Dashboard you can click any of the four status breakdown cards to drill into the exact list of mappings in that state — each row showing the case title, priority, script path, test name, last-synced timestamp, and a short reason (e.g. “Script file changed on disk”).