This is a port of jest-puppeteer to Vitest. Some of the documentation may still refer to Jest specific things so please report any issues.

vitest-environment-puppeteer

Run your tests using Vitest & Puppeteer 🎪✨

npm install vitest-environment-puppeteer puppeteer

Usage

Update your Vitest configuration:

import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    environment: "puppeteer",
    globalSetup:
      "node_modules/vitest-environment-puppeteer/dist/global-init.js",
  },
});

Use Puppeteer in your tests:

import "vitest-puppeteer";

describe("Google", () => {
  beforeAll(async () => {
    await page.goto("https://google.com");
  });

  it('should display "google" text on page', async () => {
    const text = await page.evaluate(() => document.body.textContent);
    expect(text).toContain("google");
  });
});

TypeScript Setup

If you’re using TypeScript, make sure to include vitest-puppeteer to include the necessary type definitions.

API

global.browser

Give access to the Puppeteer Browser.

it("should open a new page", async () => {
  const page = await browser.newPage();
  await page.goto("https://google.com");
});

global.page

Give access to a Puppeteer Page opened at start (you will use it most of time).

it("should fill an input", async () => {
  await page.type("#myinput", "Hello");
});

global.context

Give access to a browser context that is instantiated when the browser is launched. You can control whether each test has its own isolated browser context using the browserContext option in config.

global.vitestPuppeteer.debug()

Put test in debug mode.

• Jest is suspended (no timeout)
• A debugger instruction to Chromium, if Puppeteer has been launched with { devtools: true } it will stop

it("should put test in debug mode", async () => {
  await vitestPuppeteer.debug();
});

global.vitestPuppeteer.resetPage()

Reset global.page

beforeEach(async () => {
  await vitestPuppeteer.resetPage();
});

global.vitestPuppeteer.resetBrowser()

Reset global.browser, global.context, and global.page

beforeEach(async () => {
  await vitestPuppeteer.resetBrowser();
});

Config

Vitest Puppeteer uses cosmiconfig for configuration file support. This means you can configure Vitest Puppeteer via (in order of precedence):

• A "vitest-puppeteer" key in your package.json file.
• A .vitest-puppeteerrc file written in JSON or YAML.
• A .vitest-puppeteerrc.json, .vitest-puppeteerrc.yml, .vitest-puppeteerrc.yaml, or .vitest-puppeteerrc.json5 file.
• A .vitest-puppeteerrc.js, .vitest-puppeteerrc.cjs, vitest-puppeteer.config.js, or vitest-puppeteer.config.cjs file that exports an object using module.exports.
• A .vitest-puppeteerrc.toml file.

By default it looks for config at the root of the project. You can define a custom path using VITEST_PUPPETEER_CONFIG environment variable.

It should export a config object or a Promise that returns a config object.

interface VitestPuppeteerConfig {
  /**
   * Puppeteer connect options.
   * @see https://pptr.dev/api/puppeteer.connectoptions
   */
  connect?: ConnectOptions;
  /**
   * Puppeteer launch options.
   * @see https://pptr.dev/api/puppeteer.launchoptions
   */
  launch?: PuppeteerLaunchOptions;
  /**
   * Server config for `vitest-dev-server`.
   * @see https://www.npmjs.com/package/vitest-dev-server
   */
  server?: JestDevServerConfig | JestDevServerConfig[];
  /**
   * Allow to run one browser per worker.
   * @default false
   */
  browserPerWorker?: boolean;
  /**
   * Browser context to use.
   * @default "default"
   */
  browserContext?: "default" | "incognito";
  /**
   * Exit on page error.
   * @default true
   */
  exitOnPageError?: boolean;
  /**
   * Use `runBeforeUnload` in `page.close`.
   * @see https://pptr.dev/api/puppeteer.page.close
   * @default false
   */
  runBeforeUnloadOnClose?: boolean;
}

Sync config

// vitest-puppeteer.config.cjs

/** @type {import('packages/vitest-environment-puppeteer').VitestPuppeteerConfig} */
module.exports = {
  launch: {
    dumpio: true,
    headless: process.env.HEADLESS !== "false",
  },
  server: {
    command: "node server.js",
    port: 4444,
    launchTimeout: 10000,
    debug: true,
  },
};

Async config

This example uses an already running instance of Chrome by passing the active web socket endpoint to connect. This is useful, for example, when you want to connect to Chrome running in the cloud.

// vitest-puppeteer.config.cjs
const dockerHost = "http://localhost:9222";

async function getConfig() {
  const data = await fetch(`${dockerHost}/json/version`).json();
  const browserWSEndpoint = data.webSocketDebuggerUrl;
  /** @type {import('packages/vitest-environment-puppeteer').VitestPuppeteerConfig} */
  return {
    connect: {
      browserWSEndpoint,
    },
    server: {
      command: "node server.js",
      port: 3000,
      launchTimeout: 10000,
      debug: true,
    },
  };
}

module.exports = getConfig();

Create custom environment

It is possible to create a custom environment from the Jest Puppeteer's one. It is not different from creating a custom environment from "jest-environment-node". See Jest testEnvironment documentation to learn more about it.

// my-custom-environment
const VitestPuppeteerEnvironment =
  require("packages/vitest-environment-puppeteer").TestEnvironment;

class CustomEnvironment extends VitestPuppeteerEnvironment {
  // Implement your own environment
}

Inspiration

Thanks to Fumihiro Xue for his great Jest example.