Script Mapping

Introduction

What is Script Mapping?

The Script Mapping & Sync screen is where you connect the two halves of your testing world. On one side you have manual test cases — the human-written entries in your test catalog that describe what should be verified. On the other side you have automated scripts — the real test functions discovered in your codebase (Playwright, Cypress, Jest, pytest, and many more). This screen lets you draw a line between a manual case and the automated test that actually exercises it, and then keeps watch over whether that line is still trustworthy.

Think of it like a library card catalog cross-referenced against the shelves. The catalog (manual test cases) tells you a book should exist; the shelf (automated scripts) is where the book physically lives. A mapping is the call number that ties the two together. And just as books get reshelved, edited, or go missing, this screen flags when a script changes on disk, when a case is edited, or when a script file vanishes entirely — so the cross-reference never silently goes stale.

Note

In one sentence: Script Mapping is the traceability hub that links every manual test case to the automated script that covers it and continuously reports whether each link is still valid.

Why does mapping matter? Without it, automation runs in a vacuum — you have green test results but no way to say which requirements those greens actually cover. Mapping gives you automation coverage (what percentage of your manual catalog is backed by real scripts), traceability (from a requirement, to a manual case, to the exact line of code that verifies it), and drift detection (an early warning when a script and its case fall out of step). It turns a pile of passing tests into evidence you can stand behind in an audit or release sign-off.

Who this guide is for

• QA leads and test managers who need to report automation coverage and prove that critical manual cases are backed by real automation.
• Automation engineers who write the scripts and want to attach them to the manual cases they fulfil.
• Manual testers who author test cases and want to know which of their cases are already automated (so they can stop running them by hand).
• Release managers and auditors who need an end-to-end traceability trail from requirement to executable test. No coding is required to create mappings — the screen does it for you through point-and-click. You only need to be able to read the names of your test cases and recognise the script files they belong to.

Key terms

Term	What it means on this screen
Manual test case	An entry from your test catalog — has an ID, title, priority (critical/high/medium/low), and type (functional, regression, smoke, etc.). Listed on the left side of the Map Test Cases tab.
Automated script	A real test function discovered in your codebase. Belongs to a suite (a script file) and has a test name and a framework. Listed on the right side of the Map Test Cases tab.
Mapping	The link between one manual test case and one automated script test. Stored as testCaseId + scriptPath + testName + framework. One case can be mapped to more than one test (see Map Also).
Automation coverage	The share of your manual catalog that has at least one mapping. Shown on the Dashboard as the Mapped percentage (mapped ÷ total test cases).
Sync status	Per-mapping health: synced, script_updated, script_missing, or case_updated. Tells you whether the link can still be trusted.
Sync Health	A single headline percentage = synced mappings ÷ total mappings. Your at-a-glance confidence score for the whole map.
Suite	A single script file in the Available Scripts panel. Expands to reveal the individual test functions it contains.

How it works

The screen is organised into three tabs that flow left to right through a natural workflow: Dashboard (see where you stand), Mapped Test Cases (manage what is already linked), and Map Test Cases (create new links). The active tab is remembered in the URL (?tab=dashboard|mapped|map), so you can bookmark or share a specific view.

• You create a mapping by selecting a manual case on the left and clicking Map next to a script on the right.
• You review mappings in a table that shows the case, the script path, the test name, the framework, and the live sync status.
• You remove a mapping with the Unlink action (singly or in bulk).
• Testver watches the files behind each mapping; if a script is edited or deleted, or the case itself is edited, the sync status changes colour to warn you.
• You run Check Sync Status to re-scan all mappings and refresh those statuses on demand.

Getting Started

Opening Script Mapping

1. From the Testver navigation, open Script Mapping (route /script-mapping). The header reads Script Mapping & Sync.
2. The screen opens on the Dashboard tab by default.
3. Use the three tabs under the header — Dashboard, Mapped Test Cases, Map Test Cases — to move between views.
4. If you arrived via a shared link with ?tab=map (or mapped), that tab opens directly.

Tip

Before mapping, make sure your scripts have been discovered. The Available Scripts panel is populated from the Test Explorer. If it is empty, run your test framework once (or scan via the Test Explorer) so Testver can find your suites.

The screen layout

Region	What lives there
Header bar	Title Script Mapping & Sync with a left-right arrows icon, plus the subtitle “Link test cases to automation scripts and monitor sync health”.
Tab strip	Three tabs: Dashboard (chart icon), Mapped Test Cases (link icon), Map Test Cases (left-right arrows icon). The active tab is underlined.
Dashboard tab	Four stat cards, a sync-status breakdown bar with drill-down cards, framework distribution chips, and a Quick Actions row.
Mapped Test Cases tab	Search box, sync-status filter, a bulk-action bar (when rows are selected), and a wide table of every mapping.
Map Test Cases tab	An info banner with an unmapped counter, then a two-panel layout — unmapped cases (left) and discovered scripts (right).
Success toast	A small confirmation that slides in at the top-right after any action (map, unlink, mark synced, sync check), auto-dismissing after a few seconds.
Script viewer modal	A full read-only Monaco code editor that opens when you preview a mapped script (from the Mapped Test Cases table).

At a glance

The Dashboard tab is your starting point and answers four questions instantly through its top stat cards: how many test cases exist in total, how many are Mapped (with a coverage percentage), how many are still Unmapped, and your overall Sync Health percentage. From here the Quick Actions row lets you jump straight to mapping work or trigger a fresh sync check.

The Mapping View

The heart of the screen is the Map Test Cases tab — a true two-sided view. The left column holds the things that need automation (unmapped manual cases); the right column holds the automation available to satisfy them (discovered script tests). You bridge the gap by selecting on the left and acting on the right.

The two-panel layout

Element	Meaning
Unmapped Test Cases (left panel)	Every manual case that has no mapping yet. Each row shows the case ID (mono, brand colour), the title, plus priority and type badges. A counter pill shows how many remain.
Selection radio (left)	Clicking a case selects it (highlighted with a left brand bar and a filled radio dot). Clicking it again deselects. Only one case is the active selection at a time.
Available Scripts (right panel)	The discovered test suites, grouped by file. A counter shows how many script tests are currently available to map.
Suite header (right)	A collapsible row per script file showing the suite name, the file path (mono), a framework badge, and the test count. Click to expand or collapse its tests.
Test row (right)	An individual automated test inside a suite — shows a hash icon, the test name, a framework badge, and the (truncated) file path.
Map button (right)	Appears on each test row once a case is selected on the left. Clicking it creates the mapping. Before any case is selected, the row instead reads “Select a test case first”.
Mapped chip (right)	A green badge on a test that is already mapped. The row is dimmed to show it is taken.
Show mapped toggle (right)	A switch in the panel header. Off (default) hides already-mapped tests so you focus on what is still open; on reveals them too.
Unmapped counter pill (banner)	Top of the tab: shows “N unmapped” in amber, or “All mapped ✓” in green when nothing is left.

Reading coverage at a glance

The screen signals coverage in several complementary ways. On the right panel, mapped tests carry a green Mapped chip and appear dimmed, so the eye is drawn to the work that remains. The banner pill flips from amber (“N unmapped”) to green (“All mapped ✓”) the moment your last case is linked. On the Dashboard, the Mapped stat card shows both the count and the coverage percentage against the full catalog.

Note

Testver is smart about reverse-engineered mappings. If a whole script file was auto-mapped (its mapped test names don’t correspond to any real discovered test in that suite), the entire file is treated as mapped so it doesn’t keep showing up as available work.

Controls and filters

Control	Where	Effect
Search test cases	Map tab, left panel	Filters unmapped cases by title or ID as you type. A clear (×) button resets it.
Search mapped cases	Mapped tab	Filters the mapping table by case title, script path, or test name.
Sync-status filter	Mapped tab	A dropdown to show only mappings of a chosen status: All / Synced / Script Updated / Script Missing / Case Updated.
Show mapped toggle	Map tab, right panel	Reveals or hides already-mapped script tests in the Available Scripts list.

Creating & Removing Mappings

Mapping a test case to a script

1. Open the Map Test Cases tab.
2. In the left Unmapped Test Cases panel, click the manual case you want to automate. It highlights and its radio fills.
3. In the right Available Scripts panel, find the suite (script file) that contains the matching automated test, and click its header to expand it.
4. Locate the specific test, then click its Map button.
5. A success toast confirms “Mapped successfully to <test name>”. The case disappears from the unmapped list and now appears on the Mapped Test Cases tab.

Tip

Use the left-panel search to jump to a case by ID, and the Show mapped toggle on the right (off) to keep the script list focused on tests that aren’t taken yet.

Mapping a case to multiple scripts

A single manual case can be covered by more than one automated test. When a test is already mapped and you have a case selected on the left, its row shows the green Mapped chip alongside an amber Map Also button. Click Map Also to add an additional mapping for the selected case to that same test — useful when one requirement is verified across multiple scripts.

Removing a mapping

1. Go to the Mapped Test Cases tab.
2. Find the row you want to unlink (use search or the status filter to narrow down).
3. Click the Unlink (broken-chain) icon in that row’s Actions column.
4. Confirm the prompt “Remove mapping for 1 test case(s)?”.
5. A toast confirms the unlink. The case returns to the unmapped pool and becomes available to re-map.

How scripts are suggested

There is no free-text “guess the script for me” suggester on this screen — mappings are created by explicit selection. What Testver does provide is reverse-engineering awareness: when scripts were mapped in bulk by an automated discovery pass, the screen recognises those mappings (even when the mapped test names don’t line up with currently discovered tests) and marks the whole file as mapped, so auto-generated links don’t reappear as unfinished work. The Show mapped toggle lets you surface those if you want to inspect them.

Bulk actions

On the Mapped Test Cases tab, each row has a checkbox, and the header checkbox selects or clears every visible (filtered) row at once. As soon as one or more rows are selected, a brand-coloured bulk action bar appears showing the count selected and two buttons:

Bulk action	What it does
Unlink Selected	Prompts for confirmation, then removes the mapping for every selected case in one operation.
Mark Synced	Sets the sync status of every selected mapping to synced — a fast way to clear stale-drift warnings once you’ve reviewed them.

Caution

Unlinking is a bulk operation with a single confirmation. Double-check your selection (and any active filter) before confirming — every checked row is unmapped at once and there is no per-row undo.

What Mapping Enables

Tracing a case to its automation

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 you can click the Eye (view script) action to open the actual file in a read-only code viewer that auto-scrolls to the mapped test function — closing the loop from requirement to executable line of code without leaving Testver.

Sync statuses explained

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 status	Colour	Meaning / action
Synced	Green	Test case and script file are in step. No action needed.
Script Updated	Amber	The script file was modified on disk after mapping. Review the case to confirm it still matches the script.
Script Missing	Red	The mapped script file was deleted or moved. Re-map the case to a valid file.
Case Updated	Blue	The manual case was edited after mapping. The script may need updating to reflect the change.
Not Mapped	Grey	No 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”).

Coverage reporting on the Dashboard

The Dashboard turns the map into reportable numbers. The four stat cards give Total Test Cases, Mapped (with coverage %), Unmapped, and Sync Health. A Framework Distribution section breaks your mapped automation down by framework (Playwright, Cypress, Jest, pytest, etc.) with a count chip per framework — handy for understanding the shape of your automation estate at a glance.

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 and refresh every status. Run it after a code change, a refactor, or whenever the health numbers look out of date.

Common Tasks (How Do I…?)

I want to…	Do this
Link a manual case to a script	Map Test Cases tab → select the case (left) → expand the suite (right) → click Map on the test.
Cover one case with two scripts	Select the case, then on an already-mapped test click Map Also.
Remove a single mapping	Mapped Test Cases tab → row → Unlink icon → confirm.
Remove many mappings at once	Mapped Test Cases tab → check the rows → Unlink Selected → confirm.
Clear stale drift warnings	Select the reviewed rows → Mark Synced (or the per-row Re-sync icon).
See which cases aren’t automated	Dashboard → Unmapped card, or the Map Test Cases tab’s left panel.
Check overall automation coverage	Dashboard → Mapped stat card (shows count and %).
Find mappings whose script vanished	Mapped Test Cases tab → sync-status filter → Script Missing.
Read the actual script code	Mapped Test Cases tab → row → Eye (view script) icon.
Re-validate all statuses	Dashboard → Quick Actions → Check Sync Status.
See automation by framework	Dashboard → Framework Distribution chips.

Tips & Best Practices

• Discover scripts first. The Available Scripts panel is fed by the Test Explorer. Run your framework or scan before you start mapping, or the right panel will be empty.
• Map by priority. Tackle critical and high priority cases first — the priority badges on the left panel make it easy to spot them.
• Keep the Show mapped toggle off while mapping so the right panel stays focused on tests that still need linking.
• Run Check Sync Status after refactors. Renaming or moving files is the most common cause of Script Missing — a sync check surfaces these immediately.
• Use the status filter as a worklist. Filter the Mapped tab to Script Updated or Case Updated to see exactly which links need a human review.
• Mark Synced only after you’ve reviewed. It silences the warning but doesn’t change the underlying files — confirm the case and script really do match before clearing the flag.
• Watch your coverage percentage over time — it’s the single most useful metric to report on automation progress to stakeholders.

Troubleshooting & FAQ

No scripts appear in the Available Scripts panel

No test suites have been discovered yet. The panel itself advises: run your test framework first so Testver can discover test suites, or use the Test Explorer to scan. Once suites appear, refresh the tab.

The Map button is not available

You haven’t selected a manual case yet. Each script row reads “Select a test case first” until you pick a case in the left panel. Select one and the Map buttons appear.

A mapping shows Script Missing

The script file was deleted, renamed, or moved after the mapping was made. Either restore the file at its original path, or unlink the case and re-map it to the file’s new location.

What do Script Updated and Case Updated mean?

Amber means the script file changed on disk; blue means the manual case was edited. Neither breaks the link — they are review prompts. Confirm the case and script still describe the same behaviour, fix whichever is out of date, then Mark Synced (or use the row’s Re-sync icon) to clear the flag.

My coverage numbers look out of date

Statuses don’t auto-recompute on every visit. Open the Dashboard and click Check Sync Status to re-scan all mappings and refresh the figures.

Can one test case map to more than one script?

Yes. Select the case, then use Map Also on additional tests to add further mappings for the same case.

I unlinked a mapping by mistake

There’s no undo button; the unlink takes effect after the confirmation prompt. Simply re-create the mapping from the Map Test Cases tab — the case will be back in the unmapped list, ready to link again.

A case is mapped but I never mapped it

It was mapped by an earlier discovery / reverse-engineering pass. Toggle Show mapped on to inspect those links; if one is wrong, unlink it from the Mapped Test Cases tab.

Related

• Test Cases — what’s mapped.
• Project Explorer — opens scripts.
• AI Test Gen → Reverse Engineer — bulk-create mappings from scripts.
• Runner — runs the mapped scripts.