Set up test scripts

This guide writes the test, coverage, and test:watch scripts into package.json for Jest or Vitest.

Steps

Install the test runner, or its repobuddy preset package. buddy detects the runner from either.
Terminal window
```
# Jest
pnpm add -D jest @repobuddy/jest

# Vitest
pnpm add -D vitest @repobuddy/vitest
```
Install repobuddy.
Terminal window
```
pnpm add -D repobuddy
```
Run buddy test-scripts from the project directory.
Terminal window
```
pnpm exec buddy test-scripts
```
For a package in a workspace, run it from the root and name the package:
Terminal window
```
pnpm exec buddy test-scripts --cwd packages/app
```
If the project depends on both runners, or on neither, name the runner.
Terminal window
```
pnpm exec buddy test-scripts --runner vitest
```
Read the output. added and adjusted lines are changes. A skipped line with your own command means buddy kept a customized script.

Result

For a Vitest project, package.json now holds:

{
  "scripts": {
    "test": "vitest run",
    "coverage": "vitest run --coverage",
    "test:watch": "vitest"
  }
}

For Jest the values are jest, jest --coverage, and jest --watch.

Verify

Run the command again. It prints the vitest scripts are already what they should be (or jest).
Run pnpm test.

Move from Jest to Vitest

Run the command again after you switch runners. Scripts that still hold the Jest values from the table are adjusted to the Vitest values. A script you changed by hand stays as it is.

Set up test scripts

Steps

Result

Verify

Move from Jest to Vitest

Related