eslint-plugin-test-governance 0.3.0 → 0.4.0

package/docs/rules/no-conflicting-states.md

@@ -26,27 +26,27 @@ Incorrect:
 <!-- example: invalid settings={"lifecycleTags":true} -->
 
 ```js
-test('filters by category @new @unstable', async () => {});
+test('places a limit order @new @unstable', async () => {});
 ```
 
 <!-- example: invalid settings={"lifecycleTags":true} -->
 
 ```js
-// SKIP: WEB-9
-// NEW: WEB-9
-test.skip('filters by category @new', async () => {});
+// SKIP: TRADE-9
+// NEW: TRADE-9
+test.skip('places a limit order @new', async () => {});
 ```
 
 <!-- example: invalid settings={"lifecycleTags":true} -->
 
 ```js
-test('invoice download @New', async () => {});
+test('exports the trade history as CSV @New', async () => {});
 ```
 
 <!-- example: invalid settings={"lifecycleTags":true} -->
 
 ```js
-test('loyalty points @unstabel', async () => {});
+test('shows dividend payments in the account history @unstabel', async () => {});
 ```
 
 Correct:
@@ -54,9 +54,15 @@ Correct:
 <!-- example: valid settings={"lifecycleTags":true} -->
 
 ```js
-test('filters by category @unstable', async () => {});
+test('places a limit order @unstable', async () => {});
 ```
 
 ## Options
 
-Uses the shared options described in the [README](../../README.md#options).
+This rule has no options of its own. It reads the shared options described in the
+[README](../../README.md#options). These change what it reports:
+
+- `lifecycleTags`, or `states` for `new` and `unstable`: the `@new` checks run when the `new` state
+  is on, and `@new` together with `@unstable` is reported when both are on.
+- `customStates`: the tags of custom states get the same case and typo checks.
+- `framework` and `testFunctions`: which functions count as the framework's `test`.

package/docs/rules/no-orphaned-marker.md

@@ -22,14 +22,18 @@ one from this.
 A `FIXME:` or `TODO:` comment that starts with a valid ticket is treated by where it sits:
 
 - Above a helper or any other code that isn't a test, it is a tracked work comment and is allowed.
-- Above a test, describe or skip call that is not in the `fixme` state, it reads as a leftover marker
-  and is reported, since `// FIXME: WEB-12` above a test usually means the test was fixed and the
-  marker forgotten. Move a work comment into the test body, or onto the line of code it is about.
+- Above a test, describe or skip call that is not in the `fixme` state, a `FIXME:` comment reads as a
+  leftover marker and is reported, since `// FIXME: TRADE-12` above a test usually means the test was
+  fixed and the marker forgotten. Move a work comment into the test body, or onto the line of code it
+  is about.
+- Above a Jest or Vitest test that is not a todo, a `TODO:` comment is a tracked work comment about
+  the test and is allowed. `TODO` is the everyday keyword for such comments, so there it is far more
+  often a note than the forgotten marker of a `test.todo`.
 
 Other markers that read as a sentence, such as `// SKIP: this one is flaky`, are left alone too: the rule
 counts a comment as prose when its first word is not a valid ticket and more text follows.
 
-Files that don't use Playwright, such as application code, are not checked.
+Files without tests, such as application code, are not checked.
 
 The rule offers a suggestion to delete the comment.
 
@@ -40,16 +44,16 @@ Incorrect:
 <!-- example: invalid settings={"lifecycleTags":true} -->
 
 ```js
-// NEW: WEB-80 promoted last sprint
-test('saved addresses', async () => {});
+// NEW: TRADE-80 promoted last sprint
+test('saves a watchlist', async () => {});
 ```
 
 <!-- example: invalid -->
 
 ```js
-test('checkout', async ({ page }) => {
-  // SKIP: WEB-81
-  await page.goto('/checkout');
+test('places a limit order', async ({ page }) => {
+  // SKIP: TRADE-81
+  await page.goto('/orders');
 });
 ```
 
@@ -58,27 +62,37 @@ Correct:
 <!-- example: valid settings={"lifecycleTags":true} -->
 
 ```js
-test('saved addresses', async () => {});
+test('saves a watchlist', async () => {});
 ```
 
 <!-- example: valid -->
 
 ```js
-test('checkout', async ({ page }) => {
-  // FIXME: the banner sometimes covers the button on slow machines
-  await page.goto('/checkout');
+test('places a limit order', async ({ page }) => {
+  // FIXME: the price field sometimes loses focus on slow machines
+  await page.goto('/orders');
 });
 ```
 
 <!-- example: valid -->
 
 ```js
-// FIXME: WEB-81
-test.fixme('checkout', async ({ page }) => {
-  await page.goto('/checkout');
+// FIXME: TRADE-81
+test.fixme('places a limit order', async ({ page }) => {
+  await page.goto('/orders');
 });
 ```
 
 ## Options
 
-Uses the shared options described in the [README](../../README.md#options).
+This rule has no options of its own. It reads the shared options described in the
+[README](../../README.md#options). These change what it reports:
+
+- `lifecycleTags`, `states` and `customStates`: which keywords are markers. `// NEW:` is a marker
+  only while the `new` state is on, so with `lifecycleTags` off it is an ordinary comment.
+- `ticket` and `placeholders`: whether a comment starts with a valid ticket, which separates a
+  leftover marker from a sentence or a work comment.
+- `allowBlankLine`: whether a marker separated from the code below it by a blank line still belongs
+  to that code.
+- `framework` and `testFunctions`: which functions count as the framework's `test`, and so which
+  files are test files.

package/docs/rules/require-ticket-in-comments.md

@@ -13,12 +13,12 @@ A `// TODO: clean this up` comment is a promise nobody tracks. This rule makes e
 source of truth and nothing is forgotten in a comment.
 
 ```ts
-// TODO: WEB-512                 ✓
-// FIXME: WEB-77, WEB-78         ✓ several tickets, separated by commas
-// TODO(WEB-512)                 ✓ the ticket can go in parentheses
-// TODO(alice): refactor this    ✖ a name is not a ticket
-// TODO: refactor this           ✖ no ticket
-// FIXME: WEB-77 flaky locator   ✖ only tickets are allowed (allowNotes: true allows the note)
+// TODO: TRADE-512                 ✓
+// FIXME: TRADE-77, TRADE-78       ✓ several tickets, separated by commas
+// TODO(TRADE-512)                 ✓ the ticket can go in parentheses
+// TODO(alice): refactor this      ✖ a name is not a ticket
+// TODO: refactor this             ✖ no ticket
+// FIXME: TRADE-77 flaky locator   ✖ only tickets are allowed (allowNotes: true allows the note)
 ```
 
 How comments are read:
@@ -26,13 +26,14 @@ How comments are read:
 - The keyword starts the comment (or a line of a block comment). `TODO` and `FIXME` in capitals
   count with or without a colon. Other casings, such as `todo:`, need the colon, so a sentence that
   happens to start with "Todo" is left alone.
-- The tickets can also go in parentheses straight after the keyword, `TODO(WEB-512)`, a style many
-  teams already use. Anything after the parentheses is a note, as it would be after `TODO: WEB-512`.
+- The tickets can also go in parentheses after the keyword, `TODO(TRADE-512)` or `TODO (TRADE-512)`, a
+  style many teams already use. Anything after the parentheses is a note, as it would be after `TODO: TRADE-512`.
 - The tickets follow the same rules as markers: the shared ticket format, placeholders such as `TBD`
   rejected, and no text after the tickets unless `allowNotes` is set.
-- A `// FIXME:` marker directly above a `test.fixme(...)` is checked by
-  [`require-ticket`](require-ticket.md) instead, so it is reported once.
-- Only files that use Playwright (a Playwright import or a call to a test function) are checked.
+- A `// FIXME:` marker directly above a `test.fixme(...)`, or a `// TODO:` marker above a Jest or
+  Vitest `test.todo(...)`, is checked by [`require-ticket`](require-ticket.md) instead, so it is
+  reported once.
+- Only test files (a test framework import or a call to a test function) are checked.
   Application code is left alone, even if your config applies the plugin to it.
 
 ## Examples
@@ -42,9 +43,9 @@ Incorrect:
 <!-- example: invalid -->
 
 ```js
-test('checkout', async ({ page }) => {
+test('places a limit order', async ({ page }) => {
   // FIXME: this locator breaks on mobile
-  await page.click('#pay');
+  await page.click('#buy');
 });
 ```
 
@@ -52,7 +53,7 @@ test('checkout', async ({ page }) => {
 
 ```js
 // TODO: TBD
-test('refund', async ({ page }) => {});
+test('cancels an open order', async ({ page }) => {});
 ```
 
 Correct:
@@ -60,17 +61,17 @@ Correct:
 <!-- example: valid -->
 
 ```js
-test('checkout', async ({ page }) => {
-  // FIXME: WEB-81
-  await page.click('#pay');
+test('places a limit order', async ({ page }) => {
+  // FIXME: TRADE-81
+  await page.click('#buy');
 });
 ```
 
 <!-- example: valid settings={"comments":{"keywords":["FIXME"]}} -->
 
 ```js
-// TODO: add a refund test once the API is stable
-test('checkout', async ({ page }) => {});
+// TODO: add a test for cancelled orders once the API is stable
+test('places a limit order', async ({ page }) => {});
 ```
 
 ## Options
@@ -78,7 +79,10 @@ test('checkout', async ({ page }) => {});
 This rule has no options of its own. It reads the shared options described in the
 [README](../../README.md#options):
 
-- `comments`: the keywords to check, `{ keywords: ['FIXME', 'TODO'] }` by default. Use
-  `{ keywords: ['FIXME'] }` to allow free-form `TODO`s, add your own such as `HACK`, or set
-  `comments: false` to turn the check off. Turning the rule off in your config works too.
+- `comments`: the keywords to check, `{ keywords: ['FIXME', 'TODO'] }` by default. Your list
+  replaces the default one: `{ keywords: ['FIXME'] }` allows free-form `TODO`s, and
+  `{ keywords: ['FIXME', 'TODO', 'HACK'] }` checks `HACK` too. `comments: false` turns the check
+  off, and so does turning the rule off in your config.
 - `ticket`, `placeholders` and `allowNotes` work as they do for markers.
+- `framework` and `testFunctions`: which functions count as the framework's `test`, and so which
+  files are test files.

package/docs/rules/require-ticket.md

@@ -13,51 +13,59 @@ at the ticket that explains it, so disabled tests show up in planning instead of
 
 A test is in a state when it is:
 
-| State          | Put there by                                                                               | Marker                 | On by default              |
-| -------------- | ------------------------------------------------------------------------------------------ | ---------------------- | -------------------------- |
-| `skip`         | `test.skip('title', fn)`, `test.describe.skip`, `test.skip()` in a body, `testInfo.skip()` | `// SKIP:`             | yes                        |
-| `fixme`        | `test.fixme(...)`, `test.describe.fixme`, `testInfo.fixme()`                               | `// FIXME:`            | yes                        |
-| `new`          | the `@new` tag                                                                             | `// NEW:`              | with `lifecycleTags: true` |
-| `unstable`     | the `@unstable` tag                                                                        | `// UNSTABLE:`         | with `lifecycleTags: true` |
-| `fail`, `slow` | `test.fail(...)`, `test.slow()`                                                            | `// FAIL:`, `// SLOW:` | no                         |
-| custom         | any tag you list in `customStates`                                                         | your keyword           | when configured            |
-
-Tags are read from the title (`'checkout @new'`) and from `{ tag: '@new' }` or `{ tag: ['@new', '@smoke'] }`.
+| State          | Put there by                                                                                                                          | Marker                 | On by default              |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | -------------------------- |
+| `skip`         | `test.skip('title', fn)`, `test.describe.skip`, `test.skip()` in a body, `testInfo.skip()`, `test.step.skip`, `step.skip()` in a step | `// SKIP:`             | yes                        |
+| `fixme`        | `test.fixme(...)`, `test.describe.fixme`, `testInfo.fixme()`                                                                          | `// FIXME:`            | yes                        |
+| `todo`         | Jest's and Vitest's `test.todo`                                                                                                       | `// TODO:`             | yes, in Jest and Vitest    |
+| `new`          | the `@new` tag                                                                                                                        | `// NEW:`              | with `lifecycleTags: true` |
+| `unstable`     | the `@unstable` tag                                                                                                                   | `// UNSTABLE:`         | with `lifecycleTags: true` |
+| `fail`, `slow` | `test.fail(...)`, `test.slow()`, `testInfo.fail()`, `testInfo.slow()`                                                                 | `// FAIL:`, `// SLOW:` | no                         |
+| custom         | any tag you list in `customStates`                                                                                                    | your keyword           | when configured            |
+
+In Jest and Vitest, `xit`, `xdescribe`, Vitest's `{ skip: true }` and `context.skip()` skip a test
+too, and `test.failing` and `test.fails` put it in the `fail` state. The
+[README](../../README.md#jest-and-vitest) lists every form.
+
+Tags are read from the title (`'places a limit order @new'`) and from `{ tag: '@new' }` or `{ tag: ['@new', '@smoke'] }`.
 Tags on a `describe` apply to every test inside it.
 
 ## Marker format
 
 ```text
-// SKIP: WEB-123
-// SKIP: WEB-123, WEB-124
-/* FIXME: https://github.com/acme/web/issues/4821 */
+// SKIP: TRADE-123
+// SKIP: TRADE-123, TRADE-124
+/* FIXME: https://github.com/acme/trading-engine/issues/4821 */
 ```
 
 - The marker goes in the comment block directly above the test, describe or `test.skip()` call.
   Other comments, such as `eslint-disable-next-line`, may sit in the same block. A blank line ends
   the block unless `allowBlankLine` is set.
-- The keyword is uppercase and followed by a colon. `// skip: WEB-1` is reported with a hint.
+- The keyword is uppercase and followed by a colon. `// skip: TRADE-1` is reported with a hint.
 - After the colon come one or more tickets separated by commas, and nothing else. The ticket is the
   source of truth, so the reason for a skip belongs in the ticket, not in the comment.
-  `// SKIP: WEB-123 flaky on CI` is reported, with a suggestion that removes the extra text. Teams
+  `// SKIP: TRADE-123 flaky on CI` is reported, with a suggestion that removes the extra text. Teams
   that want short notes can set `allowNotes: true`.
 - A marker on a skipped or tagged `describe` covers every test inside it.
 - A `test.skip()` inside a test body can have its marker above the call or above the test.
-- Ticket IDs in test titles (`'SDQA-52: logout'`) are never read as tickets.
+- A skipped step, `test.step.skip(...)` or `step.skip()` in its body, can have its marker above the
+  call, above the step or above a skipped test around it. A `test.skip()` inside a step skips the
+  whole test, so its marker goes above the call or above the test.
+- Ticket IDs in test titles (`'TRADE-52: closes all positions'`) are never read as tickets.
 
 How ticket lists are read:
 
-| Marker                                                                          | Result                                                    |
-| ------------------------------------------------------------------------------- | --------------------------------------------------------- |
-| `// SKIP: WEB-1, WEB-2` or `// SKIP: WEB-1,WEB-2`                               | two tickets                                               |
-| `// SKIP:   WEB-1  ,  WEB-2  `                                                  | two tickets; extra spaces are fine                        |
-| `// SKIP: https://acme.atlassian.net/browse/WEB-1?focusedCommentId=5#comment-5` | one ticket; query strings and fragments are part of a URL |
-| `// SKIP: WEB-1 flaky on CI`, `// SKIP: WEB-1: flaky`                           | extra text `flaky on CI` / `: flaky`                      |
-| `// SKIP: WEB-1.` or `// SKIP: WEB-1:`                                          | one ticket; a full stop or colon at the end is fine       |
-| `// SKIP: WEB-1,`                                                               | extra text `,`                                            |
-| `// SKIP: WEB-1 and WEB-2`                                                      | extra text `and WEB-2`; separate tickets with commas      |
-| `// SKIP: WEB-1;WEB-2`, `// SKIP: WEB-1/WEB-2`                                  | invalid ticket, since only commas separate tickets        |
-| `// SKIP: flaky on CI`                                                          | invalid ticket `flaky`: the first word must be a ticket   |
+| Marker                                                                            | Result                                                    |
+| --------------------------------------------------------------------------------- | --------------------------------------------------------- |
+| `// SKIP: TRADE-1, TRADE-2` or `// SKIP: TRADE-1,TRADE-2`                         | two tickets                                               |
+| `// SKIP:   TRADE-1  ,  TRADE-2  `                                                | two tickets; extra spaces are fine                        |
+| `// SKIP: https://acme.atlassian.net/browse/TRADE-1?focusedCommentId=5#comment-5` | one ticket; query strings and fragments are part of a URL |
+| `// SKIP: TRADE-1 flaky on CI`, `// SKIP: TRADE-1: flaky`                         | extra text `flaky on CI` / `: flaky`                      |
+| `// SKIP: TRADE-1.` or `// SKIP: TRADE-1:`                                        | one ticket; a full stop or colon at the end is fine       |
+| `// SKIP: TRADE-1,`                                                               | extra text `,`                                            |
+| `// SKIP: TRADE-1 and TRADE-2`                                                    | extra text `and TRADE-2`; separate tickets with commas    |
+| `// SKIP: TRADE-1;TRADE-2`, `// SKIP: TRADE-1/TRADE-2`                            | invalid ticket, since only commas separate tickets        |
+| `// SKIP: flaky on CI`                                                            | invalid ticket `flaky`: the first word must be a ticket   |
 
 In a block comment, only the marker line is checked, so a JSDoc block can explain the skip on other
 lines. Extra text is reported only once the tickets on that line are valid.
@@ -66,11 +74,34 @@ Conditional skips such as `test.skip(browserName === 'webkit', 'Not supported')`
 permanent platform limit, so they need no ticket unless you set `requireTicketForConditional: true`.
 A runtime skip under an `if`, a `switch` case, a ternary or `&&` counts as conditional too, since
 `if (!enabled) test.skip()` does the same as `test.skip(!enabled)`. So does a skip in a `catch` block,
-such as `catch { test.skip(true, 'Mail server is down') }`, and a skip after an early exit such as
+such as `catch { test.skip(true, 'Market data feed is down') }`, and a skip after an early exit such as
 `if (ready) return;` or `if (!ok) throw error;` earlier in the same function.
 
 If one test or describe has several markers for the same state, each must be valid: in
-`// SKIP: WEB-1` followed by `// SKIP: nope`, the second line is reported.
+`// SKIP: TRADE-1` followed by `// SKIP: nope`, the second line is reported.
+
+## Dynamic titles
+
+Tags can only be read from a title that is text: a string or a template literal such as
+`` `buys ${symbol} @new` ``. A title built another way, such as `'buys ' + symbol` or a variable, may
+hide a tag. With `reportDynamicTitles: true`, the rule reports those titles whenever a tag state
+(`@new`, `@unstable` or a custom state) is on, so no tagged test slips past.
+
+<!-- example: invalid settings={"lifecycleTags":true,"reportDynamicTitles":true} -->
+
+```js
+for (const symbol of ['AAPL', 'MSFT']) {
+  test('buys ' + symbol, async ({ page }) => {});
+}
+```
+
+<!-- example: valid settings={"lifecycleTags":true,"reportDynamicTitles":true} -->
+
+```js
+for (const symbol of ['AAPL', 'MSFT']) {
+  test(`buys ${symbol}`, async ({ page }) => {});
+}
+```
 
 ## Examples
 
@@ -79,34 +110,40 @@ Incorrect:
 <!-- example: invalid -->
 
 ```js
-test.skip('pays with PayPal', async ({ page }) => {});
+test.skip('rejects a margin order above the buying power', async ({ page }) => {});
 ```
 
 <!-- example: invalid -->
 
 ```js
 // SKIP: flaky on CI
-test.skip('pays with PayPal', async ({ page }) => {});
+test.skip('rejects a margin order above the buying power', async ({ page }) => {});
 ```
 
 <!-- example: invalid -->
 
 ```js
 // SKIP: TODO
-test.skip('pays with PayPal', async ({ page }) => {});
+test.skip('rejects a margin order above the buying power', async ({ page }) => {});
 ```
 
 <!-- example: invalid -->
 
 ```js
-// SKIP: WEB-481 payment sandbox is down
-test.skip('pays with PayPal', async ({ page }) => {});
+// SKIP: TRADE-481 broker sandbox is down
+test.skip('rejects a margin order above the buying power', async ({ page }) => {});
 ```
 
 <!-- example: invalid settings={"lifecycleTags":true} -->
 
 ```js
-test('one-click reorder @new', async ({ page }) => {});
+test('closes all positions with one click @new', async ({ page }) => {});
+```
+
+<!-- example: invalid settings={"framework":"jest"} -->
+
+```js
+it.todo('caps position size at 2% of equity');
 ```
 
 Correct:
@@ -114,24 +151,24 @@ Correct:
 <!-- example: valid -->
 
 ```js
-// SKIP: WEB-481
-test.skip('pays with PayPal', async ({ page }) => {});
+// SKIP: TRADE-481
+test.skip('rejects a margin order above the buying power', async ({ page }) => {});
 ```
 
 <!-- example: valid -->
 
 ```js
-// FIXME: WEB-12
-test.describe.fixme('tax rules', () => {
-  test('per region', async () => {});
-  test('per product', async () => {});
+// FIXME: TRADE-12
+test.describe.fixme('risk limits', () => {
+  test('stops trading at the daily loss limit', async () => {});
+  test('caps position size at 2% of equity', async () => {});
 });
 ```
 
 <!-- example: valid -->
 
 ```js
-test('opens the dashboard', async ({ page, browserName }) => {
+test('draws the price chart', async ({ page, browserName }) => {
   test.skip(browserName === 'webkit', 'Layout differs on WebKit by design');
 });
 ```
@@ -139,18 +176,41 @@ test('opens the dashboard', async ({ page, browserName }) => {
 <!-- example: valid settings={"allowNotes":true} -->
 
 ```js
-// SKIP: WEB-481 payment sandbox is down
-test.skip('pays with PayPal', async ({ page }) => {});
+// SKIP: TRADE-481 broker sandbox is down
+test.skip('rejects a margin order above the buying power', async ({ page }) => {});
 ```
 
 <!-- example: valid settings={"lifecycleTags":true} -->
 
 ```js
-// NEW: WEB-77
-test('one-click reorder', { tag: '@new' }, async ({ page }) => {});
+// NEW: TRADE-77
+test('closes all positions with one click', { tag: '@new' }, async ({ page }) => {});
+```
+
+<!-- example: valid settings={"framework":"vitest"} -->
+
+```js
+import { describe, test } from 'vitest';
+
+describe('risk limits', () => {
+  // TODO: TRADE-90
+  test.todo('caps position size at 2% of equity');
+
+  test.skipIf(process.env.CI)('streams live quotes', () => {});
+});
 ```
 
 ## Options
 
 This rule has no options of its own. It reads the shared options described in the
-[README](../../README.md#options), usually set once with `testGovernance.configure({...})`.
+[README](../../README.md#options), usually set once with `testGovernance.configure({...})`. These
+change what it reports:
+
+- `ticket` and `placeholders`: which tickets are accepted.
+- `lifecycleTags`, `states` and `customStates`: which states need a marker, what the marker is
+  called, and, for a state with its own `ticket`, which tickets it accepts.
+- `requireTicketForConditional`: conditional skips need a ticket too.
+- `allowBlankLine`: blank lines may separate a marker from its test.
+- `allowNotes`: text may follow the tickets.
+- `reportDynamicTitles`: report titles whose tags can't be read (see [Dynamic titles](#dynamic-titles)).
+- `framework` and `testFunctions`: which functions count as the framework's `test`.

package/package.json

@@ -1,12 +1,14 @@
 {
   "name": "eslint-plugin-test-governance",
-  "version": "0.3.0",
-  "description": "ESLint rules that require a ticket comment above skipped, fixme and tagged Playwright tests.",
+  "version": "0.4.0",
+  "description": "ESLint rules that require a ticket comment above skipped, fixme, todo and tagged Playwright, Jest and Vitest tests.",
   "keywords": [
     "eslint",
     "eslintplugin",
     "eslint-plugin",
     "playwright",
+    "jest",
+    "vitest",
     "testing"
   ],
   "homepage": "https://github.com/Huldoser/eslint-plugin-test-governance#readme",
@@ -35,7 +37,6 @@
   "types": "./dist/index.d.ts",
   "files": [
     "dist",
-    "!dist/**/*.map",
     "docs",
     "CHANGELOG.md"
   ],
@@ -45,8 +46,8 @@
   "scripts": {
     "build": "node -e \"require('node:fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.build.json",
     "typecheck": "tsc -p tsconfig.json",
-    "test": "vitest run",
-    "test:coverage": "vitest run --coverage",
+    "test": "node --test 'tests/**/*.test.ts'",
+    "test:coverage": "node --test --experimental-test-coverage --test-coverage-include='src/**' --test-coverage-branches=100 --test-coverage-functions=100 --test-coverage-lines=100 'tests/**/*.test.ts'",
     "test:pack": "node scripts/pack-smoke.mjs",
     "docs": "npm run build && eslint-doc-generator",
     "docs:check": "npm run build && eslint-doc-generator --check",
@@ -63,15 +64,11 @@
     "@types/node": "^26.6.3",
     "@typescript-eslint/parser": "^8.71.0",
     "@typescript-eslint/utils": "^8.71.0",
-    "@vitest/coverage-v8": "^5.0.2",
     "eslint": "^10.11.0",
-    "eslint-config-prettier": "^10.1.8",
     "eslint-doc-generator": "^3.7.1",
     "eslint-plugin-eslint-plugin": "^7.6.2",
-    "globals": "^17.13.0",
     "prettier": "^3.9.9",
     "typescript": "6.0",
-    "typescript-eslint": "^8.71.0",
-    "vitest": "^5.0.2"
+    "typescript-eslint": "^8.71.0"
   }
 }