E2E Coverage Gaps
On runtimes without the rule tree (Antigravity), read Worth doing in lisa-track for the same value and decline policy.
Overview
Find where the automated end-to-end (Playwright) suite is blind: routes with no test at all, and
flows that only assert the happy path while ignoring error, permission, empty, loading, and edge
cases. Inventory the app's routes and the existing tests, explore the running app to confirm each gap
is real and reachable, then group worthwhile gaps into bounded build-ready missing-test work items so it enters the
Lisa lifecycle.
This skill is purely about automated-coverage gaps. It does not judge whether the UI is confusing
or pretty — for human usability findings, use the lisa-exploratory-qa skill.
Parameters
target-url | env (first positional) — the app to inventory and explore.
ready=true|false — build-ready state for the missing-test tickets (default true). Adding
missing coverage is safe to queue, so these default to build-ready; pass ready=false to leave them
in the backlog for human triage.
Core Workflow
1. Establish Scope
- Identify the target environment, account type, and browser requirement, and read the
ready flag
(default true).
- Confirm the tracker is configured. Gaps are filed as tickets, so read
tracker from
.lisa.config.json (local overrides global). If it is unset, stop and report that the tracker must
be configured (via /lisa:setup:jira / :github / :linear) before gaps can be filed.
2. Inventory App Routes
- Enumerate every route/screen from the project's routing source — filesystem routes, the router
config, navigation definitions, or a generated sitemap.
- For each route capture: its path + params, the auth/role it requires, and the primary user actions
reachable from it (forms, mutations, filters, flows).
3. Inventory Existing Playwright Coverage
- Inspect the Playwright config, auth/setup projects, fixtures, constants, selectors, spec directories,
skipped/TODO/flaky tests, retries, and viewport/device projects.
- For each spec, record which route(s)/flow(s) it exercises and whether it asserts behavior or just
presence.
- Use existing test helpers/selectors when exploring — they reveal intended flows and stable hooks.
4. Compute the Gap Matrix
Map routes/flows against existing coverage and classify each gap:
- Uncovered route/flow: no test touches it at all.
- Happy-path-only: the success case is tested but the non-happy paths are not — missing
error/validation, permission/denied, empty/zero-state, loading/slow, and boundary/edge scenarios.
- Assertion-thin: a test exists but asserts presence rather than behavior/outcome.
- Skipped/TODO/flaky: coverage exists but is disabled or unreliable.
- Breakpoint gap: a flow is only tested at a single viewport when behavior changes across
breakpoints.
5. Explore to Confirm
- Apply
do-it-now's Worth doing guidance: missing coverage alone is not a defect. Identify a required behavior or credible material risk; decline low-value gaps without filing and group related accepted gaps.
- Navigate each candidate gap in the running app to confirm it is real, reachable, and worth a test.
Discard gaps that aren't actually reachable or are intentionally out of scope.
6. File Bounded Work for Accepted Gaps
Each accepted gap or coherent group becomes a leaf missing-test work item created via lisa-tracker-write (the
vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
call a vendor *-write-* skill directly), issue_type: Task, build-ready per the ready flag
(default true). For ready=true, pass build_ready: true. For ready=false,
pass human_gate: "Coverage work explicitly held for operator prioritization" instead.
Each ticket MUST specify:
- The route/flow and the exact user behavior the test must assert.
- Which scenario is missing (uncovered vs which non-happy path: error / validation / permission /
empty / loading / edge / breakpoint).
- The stable selector / fixture / flow to use — concrete and automatable.
- Three-audience description + Gherkin acceptance criteria describing the test to add.
Idempotency — don't spam duplicates
Before creating a ticket, follow rejection-detection — Proposal rejection memory:
use <!-- [lisa-e2e-coverage-gaps] key=<candidate-key> --> with the normalized route +
missing scenario hashed deterministically by that rule's existing formula. Search open AND
closed tickets, including its body-enumeration fallback for search-index lag. Match by the
marker for any constituent gap, never by title alone. Reuse open matches. For legacy issues
without a marker or with the older [lisa-e2e-coverage-gaps] <gap-key> slug marker, read
bodies and closing discussions to establish a semantic match; title similarity
alone is insufficient. A Not planned decision suppresses the same accepted
limitation, even when seen again later. Re-propose only for a materially changed
consequence, requirement, or risk that addresses the decline. A completed fix may
have a real regression, which must be verified before filing. Grouped work retains
the constituent gap markers so a later pass can find it.
Output
No report file. Emit a concise in-session summary:
- Route inventory: count of routes/screens discovered.
- Existing coverage: strengths and thin areas (skipped/flaky, assertion-thin, single-viewport).
- Gap matrix: uncovered vs happy-path-only vs breakpoint gaps.
- Tickets filed: each gap with its created/referenced ticket ref and build-ready state.
Quality Bar
- Distinguish no coverage from happy-path-only — both are gaps, but the ticket must say which.
- Every ticket must stand alone for an implementer who was not in the session and must be concretely
automatable (named route, behavior, and stable hook).
- Do not refile gaps already covered or already ticketed (marker check).
- This skill is about automated coverage only — route human usability issues to
lisa-exploratory-qa.
- Preserve unrelated repo changes.
1---2name: e2e-coverage-gaps-33description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files bounded build-ready work for worthwhile test gaps via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.4metadata:5 source: https://skillmd.com/skills/codyswanngt/e2e-coverage-gaps-36---78# E2E Coverage Gaps910On runtimes without the rule tree (Antigravity), read **Worth doing** in `lisa-track` for the same value and decline policy.1112## Overview1314Find where the automated end-to-end (Playwright) suite is **blind**: routes with no test at all, and15flows that only assert the **happy path** while ignoring error, permission, empty, loading, and edge16cases. Inventory the app's routes and the existing tests, explore the running app to confirm each gap17is real and reachable, then group worthwhile gaps into **bounded build-ready missing-test work items** so it enters the18Lisa lifecycle.1920This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing21or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.2223## Parameters2425- **`target-url | env`** (first positional) — the app to inventory and explore.26- **`ready=true|false`** — build-ready state for the missing-test tickets (**default `true`**). Adding27 missing coverage is safe to queue, so these default to build-ready; pass `ready=false` to leave them28 in the backlog for human triage.2930## Core Workflow3132### 1. Establish Scope3334- Identify the target environment, account type, and browser requirement, and read the `ready` flag35 (default `true`).36- **Confirm the tracker is configured.** Gaps are filed as tickets, so read `tracker` from37 `.lisa.config.json` (local overrides global). If it is unset, stop and report that the tracker must38 be configured (via `/lisa:setup:jira` / `:github` / `:linear`) before gaps can be filed.3940### 2. Inventory App Routes4142- Enumerate every route/screen from the project's routing source — filesystem routes, the router43 config, navigation definitions, or a generated sitemap.44- For each route capture: its path + params, the auth/role it requires, and the primary user actions45 reachable from it (forms, mutations, filters, flows).4647### 3. Inventory Existing Playwright Coverage4849- Inspect the Playwright config, auth/setup projects, fixtures, constants, selectors, spec directories,50 skipped/TODO/flaky tests, retries, and viewport/device projects.51- For each spec, record which route(s)/flow(s) it exercises and whether it asserts **behavior** or just52 **presence**.53- Use existing test helpers/selectors when exploring — they reveal intended flows and stable hooks.5455### 4. Compute the Gap Matrix5657Map routes/flows against existing coverage and classify each gap:5859- **Uncovered route/flow:** no test touches it at all.60- **Happy-path-only:** the success case is tested but the non-happy paths are not — missing61 error/validation, permission/denied, empty/zero-state, loading/slow, and boundary/edge scenarios.62- **Assertion-thin:** a test exists but asserts presence rather than behavior/outcome.63- **Skipped/TODO/flaky:** coverage exists but is disabled or unreliable.64- **Breakpoint gap:** a flow is only tested at a single viewport when behavior changes across65 breakpoints.6667### 5. Explore to Confirm6869- Apply `do-it-now`'s **Worth doing** guidance: missing coverage alone is not a defect. Identify a required behavior or credible material risk; decline low-value gaps without filing and group related accepted gaps.70- Navigate each candidate gap in the running app to confirm it is real, reachable, and worth a test.71 Discard gaps that aren't actually reachable or are intentionally out of scope.7273### 6. File Bounded Work for Accepted Gaps7475Each accepted gap or coherent group becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the76vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never77call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag78(default `true`)**. For `ready=true`, pass `build_ready: true`. For `ready=false`,79pass `human_gate: "Coverage work explicitly held for operator prioritization"` instead.80Each ticket MUST specify:8182- The **route/flow** and the exact **user behavior the test must assert**.83- **Which scenario is missing** (uncovered vs which non-happy path: error / validation / permission /84 empty / loading / edge / breakpoint).85- The **stable selector / fixture / flow** to use — concrete and automatable.86- **Three-audience description** + **Gherkin acceptance criteria** describing the test to add.8788### Idempotency — don't spam duplicates8990Before creating a ticket, follow `rejection-detection` — **Proposal rejection memory**:91use `<!-- [lisa-e2e-coverage-gaps] key=<candidate-key> -->` with the normalized route +92missing scenario hashed deterministically by that rule's existing formula. Search open AND93closed tickets, including its body-enumeration fallback for search-index lag. Match by the94marker for any constituent gap, never by title alone. Reuse open matches. For legacy issues95without a marker or with the older `[lisa-e2e-coverage-gaps] <gap-key>` slug marker, read96bodies and closing discussions to establish a semantic match; title similarity97alone is insufficient. A **Not planned** decision suppresses the same accepted98limitation, even when seen again later. Re-propose only for a materially changed99consequence, requirement, or risk that addresses the decline. A completed fix may100have a real regression, which must be verified before filing. Grouped work retains101the constituent gap markers so a later pass can find it.102103## Output104105No report file. Emit a concise in-session summary:106107- **Route inventory:** count of routes/screens discovered.108- **Existing coverage:** strengths and thin areas (skipped/flaky, assertion-thin, single-viewport).109- **Gap matrix:** uncovered vs happy-path-only vs breakpoint gaps.110- **Tickets filed:** each gap with its created/referenced ticket ref and build-ready state.111112## Quality Bar113114- Distinguish **no coverage** from **happy-path-only** — both are gaps, but the ticket must say which.115- Every ticket must stand alone for an implementer who was not in the session and must be concretely116 automatable (named route, behavior, and stable hook).117- Do not refile gaps already covered or already ticketed (marker check).118- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.119- Preserve unrelated repo changes.