Vv/test automation

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -18,6 +18,7 @@ body:
         - WebdriverIO (@wdio/devtools-service)
         - Nightwatch (@wdio/nightwatch-devtools)
         - Selenium WebDriver (@wdio/selenium-devtools)
+        - None — @wdio/elements used standalone
     validations:
       required: true
 
@@ -40,7 +41,7 @@ body:
     id: devtools-version
     attributes:
       label: DevTools package version
-      description: The version of the adapter package above (check your package.json or lockfile).
+      description: The version of the package you selected above (check your package.json or lockfile).
       placeholder: e.g. 0.4.2
     validations:
       required: true
@@ -72,6 +73,7 @@ body:
       options:
         - Dashboard UI (rendering, controls, rerun/stop)
         - Captured data (network, console, screencast, trace)
+        - Element snapshot / locators (getSnapshot, getElements, accessibility tree)
         - Backend / server (connection, websocket, crashes)
         - Test launch / lifecycle (hooks, session, capabilities)
         - Not sure

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -37,6 +37,7 @@ body:
       options:
         - Dashboard UI
         - Capture / reporting core
+        - Element snapshot / locator API (@wdio/elements)
         - WebdriverIO adapter
         - Nightwatch adapter
         - Selenium adapter

.github/pull_request_template.md

@@ -19,6 +19,7 @@
 
 - [ ] `shared` (types and contracts)
 - [ ] `core` (framework-agnostic capture/reporting)
+- [ ] `elements` (published element/snapshot API — `@wdio/elements`)
 - [ ] `service` (WebdriverIO adapter)
 - [ ] `nightwatch-devtools` (Nightwatch adapter)
 - [ ] `selenium-devtools` (Selenium adapter)

.github/workflows/ci.yml

@@ -8,6 +8,9 @@ on:
       - v[0-9]+.[0-9]+.[0-9]+*
   pull_request:
 
+permissions:
+  contents: read
+
 jobs:
   build:
     runs-on: ubuntu-latest
@@ -23,9 +26,9 @@ jobs:
           cache-name: cache-pnpm-modules
         with:
           path: ~/.pnpm-store
-          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ matrix.node-version }}-${{ hashFiles('**/pnpm-lock.yaml') }}
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/pnpm-lock.yaml') }}
           restore-keys: |
-            ${{ runner.os }}-build-${{ env.cache-name }}-${{ matrix.node-version }}-
+            ${{ runner.os }}-build-${{ env.cache-name }}-
       - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
         with:
           version: 10.26.1
@@ -36,5 +39,82 @@ jobs:
         run: pnpm lint
       - name: 📦 Bundle
         run: pnpm -r --workspace-concurrency=1 build
+      # Four tsc programs — see the `typecheck` script. Runs before the tests
+      # because it is fast and its failures are cheaper to read.
+      - name: 🔎 Typecheck
+        run: pnpm typecheck
+      # `test:coverage`, not `test`: same specs plus the coverage floor, ~8s
+      # more. Without it the thresholds in vitest.config.ts gate nothing.
       - name: 🧪 Run Tests
-        run: pnpm test
+        run: pnpm test:coverage
+
+  # Separate job because these are the only tests that need a real browser, and
+  # they parallelise with `build` instead of extending it. No bundle step: the
+  # specs and packages/app/src reach @wdio/devtools-shared through its source
+  # exports, so Vite compiles everything from source. Chrome comes preinstalled
+  # on the runner image; wdio fetches the matching driver itself.
+  component-tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - name: Use Node.js
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version-file: .nvmrc
+      - name: Cache pnpm modules
+        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        env:
+          cache-name: cache-pnpm-modules
+        with:
+          path: ~/.pnpm-store
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+      - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
+        with:
+          version: 10.26.1
+          run_install: false
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+      # Two workers, not the runner default: each carries a Vite server plus a
+      # Chrome, and past 2 the heaviest specs time out under that contention.
+      - name: 🧩 Component Tests
+        run: pnpm test:ui --maxInstances 2
+
+  # The component suite again, instrumented. Separate from `component-tests` so
+  # a coverage-only flake can never mask a real component failure:
+  # instrumentation costs ~16% wall clock and loses roughly one spec per run to
+  # a BiDi navigate timeout — a different one each run, which is why this is
+  # report-only for now. It measures packages/app/src, the rendering layer
+  # vitest's denominator excludes on purpose (a node test cannot import a Lit
+  # element). Drop continue-on-error and add thresholds once that flake is fixed.
+  component-coverage:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - name: Use Node.js
+        uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0
+        with:
+          node-version-file: .nvmrc
+      - name: Cache pnpm modules
+        uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
+        env:
+          cache-name: cache-pnpm-modules
+        with:
+          path: ~/.pnpm-store
+          key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/pnpm-lock.yaml') }}
+          restore-keys: |
+            ${{ runner.os }}-build-${{ env.cache-name }}-
+      - uses: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061 # v4.2.0
+        with:
+          version: 10.26.1
+          run_install: false
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+      # Two workers, not the runner default: each carries a Vite server plus a
+      # Chrome, and past 2 the heaviest specs time out under that contention.
+      - name: 📊 Component Coverage
+        env:
+          COVERAGE: '1'
+        run: pnpm test:ui --maxInstances 2

.gitignore

@@ -23,8 +23,13 @@ dist-ssr
 *.njsproj
 *.sln
 *.sw?
+# Scratch scripts and dumps dropped at the repo root. Real root-level config
+# has to be un-ignored by name: a new one is otherwise silently never added,
+# and CI then runs with different settings than everyone's checkout.
 /*.ts
 /*.json
+!/vitest.config.ts
+!/tsconfig.dts.json
 *.tgz
 examples/wdio/wdio-*.json
 examples/wdio/wdio-*.webm
@@ -55,6 +60,5 @@ examples/**/allure-results*/
 examples/**/allure-report*/
 packages/**/allure-results*/
 packages/**/allure-report*/
-examples/playwright-allure/
 examples/wdio/cucumber/wdio.allure.conf.ts
 

ARCHITECTURE.md

@@ -142,9 +142,11 @@ The execution environment is the browser, not Node, so this package cannot impor
 
 ### `packages/elements`
 
-Element-detection scripts (`@wdio/elements`). Produces the per-action data that feeds the snapshot pipeline: `getSnapshot`, the depth-indented accessibility-tree serializer, and the interactable-element list, plus locator generation.
+The WDIO-typed element-detection API (`@wdio/elements`): `getSnapshot`, `getElements`, the accessibility-tree and interactable-element readers. Unlike `shared` and `core` this package **is** published, so its exported names are public API.
 
-Consumed by `core` (the element-snapshot builder) and by the adapters' per-action capture (`captureActionSnapshot`). The DOM-walking scripts run in the page via `browser.execute`, so — like `script` — they avoid Node-only APIs.
+Imports from: `core`. The script bodies, serializers, types, and locator generation all live in `core` (`element-scripts.ts`, `element-snapshot.ts`, `element-types.ts`, `locators/`) because they're framework-agnostic; this package holds only the wrappers that take a `WebdriverIO.Browser` — which `core` can't type against. The arrow never reverses: `core` does not import `elements`, and the adapters' per-action capture (`captureActionSnapshot`) calls core's script bodies directly rather than going through this package. `elements/snapshot.ts` and `elements/locators/index.ts` are re-export shims kept for API stability.
+
+The DOM-walking scripts run in the page via `browser.execute`, so — like `script` — they avoid Node-only APIs.
 
 ### `examples/`