chore: use "test" terminology

Author: sheremet-va

.github/workflows/ci.yml

@@ -39,15 +39,11 @@ jobs:
       - name: Lint
         run: pnpm lint
 
-      # The provider source relies on provider-internal Vitest exports that only
-      # fully resolve when the package is installed alongside a matching Vitest.
-      # The JS build is the contract; typecheck is informational. See CONTRIBUTING.md.
       - name: Typecheck
         run: pnpm typecheck
-        continue-on-error: true
 
   test-browser:
-    name: Smoke (${{ matrix.os }})
+    name: Test (${{ matrix.os }})
     strategy:
       fail-fast: false
       matrix:
@@ -77,5 +73,5 @@ jobs:
       - name: Build
         run: pnpm build
 
-      - name: Smoke tests (webdriverio)
-        run: pnpm test:smoke
+      - name: Test (webdriverio)
+        run: pnpm test

.github/workflows/prepare-publish.yml

@@ -68,8 +68,8 @@ jobs:
           RELEASE_INPUT="${RELEASE_VERSION:-$RELEASE_TYPE}"
           PREPARE_BRANCH="prepare-$TARGET_BRANCH-$RELEASE_INPUT-$RUN_ID"
           git switch -c "$PREPARE_BRANCH"
-          git config user.name "vitest-release-bot[bot]"
-          git config user.email "292707936+vitest-release-bot[bot]@users.noreply.github.com"
+          git config user.name "vitest-community-release-bot[bot]"
+          git config user.email "297853836+vitest-community-release-bot[bot]@users.noreply.github.com"
           pnpm run release
 
       - id: generate-token

.github/workflows/publish.yml

@@ -111,8 +111,8 @@ jobs:
           GH_TOKEN: ${{ steps.generate-token.outputs.token }}
         run: |
           TAG="v$VERSION"
-          git config user.name "vitest-release-bot[bot]"
-          git config user.email "292707936+vitest-release-bot[bot]@users.noreply.github.com"
+          git config user.name "vitest-community-release-bot[bot]"
+          git config user.email "297853836+vitest-community-release-bot[bot]@users.noreply.github.com"
           git tag "$TAG" "$GITHUB_SHA"
           git push "https://x-access-token:$GH_TOKEN@github.com/$GITHUB_REPOSITORY.git" "$TAG"
 

CONTRIBUTING.md

@@ -21,14 +21,13 @@ This package implements the (currently experimental) browser-provider contract e
 A few couplings are intentional and accepted as compatibility risks rather than worked around:
 
 - the provider augments `vitest/node` and `vitest/browser` via `declare module`;
-- it reads `project.vitest.state._data` and `config.teardownTimeout` to extend the WebDriver shutdown timeout;
-- the locator engine assigns `__INTERNAL._createLocator` from `vitest/internal/browser`.
+- the locator engine assigns `__INTERNAL._createLocator` from `vitest/internal/browser`. That export is stripped from the published type declarations, so the import carries a `@ts-expect-error`.
 
-These resolve against whichever Vitest version the consumer installs. When upgrading the supported Vitest version, bump this package to match and re-run the smoke suite.
+These resolve against whichever Vitest version the consumer installs. When upgrading the supported Vitest version, bump this package to match and re-run the test suite.
 
-### Types vs JS
+### Types
 
-The provider source imports a handful of symbols (`page`, `server`, `utils`, `Locator`, `ScreenshotMatcherOptions`, …) from `vitest/browser`. Those are only re-exported by `vitest/browser` when a browser-provider context is installed alongside it, so a standalone `pnpm typecheck` will report unresolved members. **The JS build is the contract** — `pnpm build` is the source of truth and CI treats `typecheck` as informational (`continue-on-error`). To get a fully green typecheck/test run, develop against a matching Vitest (see below).
+`vitest/browser` only re-exports the browser context types (`page`, `server`, `utils`, `Locator`, `ScreenshotMatcherOptions`, …) through an installed provider package. Because the provider under development is the repo root and not in `node_modules`, [`tsconfig.json`](./tsconfig.json) maps `@vitest/browser-webdriverio` and `@vitest/browser-webdriverio/context` back to the local source via `paths`, so `pnpm typecheck` resolves those symbols through this package's own context. The only remaining gap is the intentionally-untyped `__INTERNAL` import (see above). Note: if a future Vitest release adds `__INTERNAL` to the published types, the `@ts-expect-error` becomes an unused directive and must be dropped.
 
 ## Developing against an unreleased Vitest
 
@@ -42,17 +41,17 @@ overrides:
 
 Do not commit the override. It is only for local development before a matching beta is published.
 
-## Smoke tests
+## Tests
 
 The suite in [`test/`](./test) is deliberately small. It does not re-test Vitest browser-mode behavior (that is Vitest's responsibility); it proves the WebdriverIO provider implements the contract and that its commands/locators/CDP/screenshots work against a real driver.
 
 ```sh
 # requires a local Chrome + chromedriver
-pnpm test:smoke
+pnpm test
 
 # pick a browser / run headed
-BROWSER=firefox pnpm test:smoke
-HEADLESS=false pnpm test:smoke
+BROWSER=firefox pnpm test
+HEADLESS=false pnpm test
 ```
 
 In CI the [`setup-webdriverio`](./.github/actions/setup-webdriverio) action installs Chrome/ChromeDriver (and optionally Firefox) and exports `CHROME_BIN` / `CHROMEDRIVER_PATH` / `FIREFOX_BIN`, which [`vitest.config.ts`](./vitest.config.ts) feeds to WebdriverIO so it does not auto-download a mismatched driver.
@@ -63,7 +62,5 @@ Releases mirror the Vitest pipeline:
 
 1. Run the **Prepare Publish** workflow (`workflow_dispatch`). It bumps the version with `bumpp` and opens a `chore: release vX.Y.Z` PR.
 2. Merge the PR. The **Publish Package** workflow detects the release commit, builds, publishes to npm via trusted publishing, pushes the `vX.Y.Z` tag, and generates a GitHub release with `changelogithub`.
-
-Versioning policy: keep the version inside the current Vitest beta range (`5.0.0-beta.x`) and move the `vitest` peer range to `^5` once Vitest 5 is stable.
-
-> The release workflows still reference the `vitest-release-bot[bot]` identity and the `RELEASE_GITHUB_APP_*` / npm trusted-publishing secrets. Update the bot identity and configure the secrets/`Release` environment for this repository before the first release.
+3. Approve the Release workflow in GitHub Actions.
+4. Approve the staged package on npm.

README.md

@@ -48,13 +48,9 @@ Then run Vitest in the browser mode:
 npx vitest --browser
 ```
 
-## Compatibility
-
-This provider builds against the published `vitest` and `@vitest/browser` packages and tracks the same major version line. The `peerDependencies` range is kept deliberately tight because the browser-provider API is still marked experimental upstream. When upgrading Vitest, upgrade this package to the matching version.
-
 ## Contributing
 
-See [CONTRIBUTING.md](./CONTRIBUTING.md) for local development, the build setup, the smoke test suite, and the release process.
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for local development, the build setup, the test suite, and the release process.
 
 ## License
 

package.json

@@ -51,7 +51,6 @@
     "lint": "eslint .",
     "lint:fix": "eslint . --fix",
     "test": "vitest run",
-    "test:smoke": "vitest run",
     "release": "tsx scripts/release.ts",
     "publish-ci": "tsx scripts/publish-ci.ts"
   },

test/user-event.test.ts

@@ -8,7 +8,7 @@ beforeEach(() => {
 })
 
 // One assertion per WebDriverIO user-event command (src/commands/*). These are
-// the highest-value smoke targets: each maps a Vitest user-event to a specific
+// the highest-value targets: each maps a Vitest user-event to a specific
 // WebDriver Actions API call and is exactly what regresses on a wdio bump.
 describe('user events', () => {
   it('click / dblClick', async () => {

vitest.config.ts

@@ -2,7 +2,7 @@ import process from 'node:process'
 import { defineConfig } from 'vitest/config'
 import { webdriverio } from './src/index'
 
-const browser = process.env.BROWSER || 'chrome'
+const browser = process.env.BROWSER as 'chrome' | 'firefox' | 'safari' || 'chrome'
 
 // In CI the `setup-webdriverio` action exports explicit binary paths so
 // WebDriverIO does not auto-download a mismatched driver. Locally these are