Skip to content
| Marketplace
Sign in
Visual Studio Code>Testing>Playwright LogbookNew to Visual Studio Code? Get it now.
Playwright Logbook

Playwright Logbook

Krishna S

|
36 installs
| (0) | Free
Browse Playwright runs, investigate failures and retries, compare test history, and import CI results.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Playwright Logbook logo

Playwright Logbook for VS Code

Browse recorded Playwright runs, inspect failures, compare history, and open evidence in your editor.

Install Playwright Logbook for VS Code

Get started

  1. Install Playwright Logbook by krishnapollu from the VS Code Marketplace.

  2. Add the reporter to your Playwright project: npm install --save-dev playwright-logbook.

  3. Add it to your existing playwright.config.ts reporter list:

    import { defineConfig } from '@playwright/test';
    
    export default defineConfig({
      reporter: [
        ['list'],
        ['playwright-logbook', { captureDetails: true }],
      ],
      use: { screenshot: 'only-on-failure', trace: 'on-first-retry' },
    });
    
  4. Run npx playwright test, then open Logbook in VS Code's activity bar.

Keep .logbook/index.jsonl and .logbook/runs/ to retain history. Open the suite or workspace root containing the history. The extension needs desktop VS Code 1.95+; the reporter needs Node.js 20+ and Playwright 1.42+.

The sidebar always shows the open workspace folder above its runs. For a monorepo, open its root folder. Logbook groups default stores in direct child suites, packages/*, and their config/ directories under that folder; Refresh rescans for newly added or removed suites. Each suite keeps separate runs and source paths. To configure a suite's custom history or source mapping, open that suite as a VS Code workspace folder and use the existing Logbook settings. For example, a new run using packages/tenant-1/config/playwright-config.js writes packages/tenant-1/.logbook/ and appears as packages/tenant-1 under the workspace. Existing packages/tenant-1/config/.logbook/ history appears as packages/tenant-1/config. Use Playwright's --config option when the config filename is not one of its defaults. Folder descriptions show saved run counts. A workspace folder's count includes its own history and every discovered child suite, independent of the loaded run page. While a test filter is active, folder descriptions switch to the matching runs currently loaded in the tree, marked shown. Search older runs extends that window and updates the counts.

Explore runs

  • One live filter: Use the field above Recent Runs to search run ID, date, title, status, branch, commit, test name, ID, project, or path. Search older runs extends the loaded window; Clear resets it.
  • Spec shortcut: Right-click a .spec.* or .test.* file in Explorer to filter to that file. Right-click inside a test in the editor to filter to that test.
  • Expand All / Collapse All: Open or close visible folders and runs in Recent Runs.
  • Run overview: Select a run's overview to see counts, project breakdown, and clickable cases. Run overviews and results open as ordinary tabs in the active editor group.
  • Runs / Tests switch: Use the switch above the filter to browse runs or the newest recorded execution of each test in the loaded window. Open a test for history and comparison, or load more runs to extend coverage.
  • HTML export: Use Export in a run overview or test detail. The single HTML file embeds retained attachments; images and videos open in a viewer, and files can be downloaded. A run export uses the reporter's report renderer with history available at export time.
  • Tests count: Each folder in Tests shows the number of distinct indexed tests in its loaded run window. Filters change the count to the number shown.
  • Run origin: Recent Runs and run overviews show Local for runs outside the import catalog, CI for fetched GitHub runs, and Peer for runs from another configured tester. Imported ZIPs without recorded origin remain unmarked. Run overviews show the recorded tester or CI provider/build/attempt when available.
Recent Runs sidebar for pw-test with Local and CI runs and an expanded CI run Filter This Test action in a pw-test spec editor context menu Current pw-test run overview showing status, duration, result distribution, project breakdown, and case table

Investigate a failure

  • Result detail: Read the recorded error, retries, source excerpt, steps, and logs. Open failure location and Open test definition jump to the current checkout.
  • Screenshots: Playwright creates screenshot files; Logbook records their metadata. captureDetails: true adds eligible failed/flaky PNG or JPEG previews and captured steps/output to new runs.
  • History and comparison: Select an earlier execution or choose Compare. The explicit committed-source diff needs Workspace Trust, local Git, and locally available recorded revisions.
Current pw-test failure detail with recorded assertion, retries, source action, and history Current pw-test comparison showing a pass-to-fail change and the shared recorded commit Diff in comparison view

Test evidence

  • Switch between attempts, then open Steps, Logs, Errors, or Attachments.
  • Click an attachment name or image preview to open the recorded file in the current editor group. Use the folder button to reveal it in Finder or File Explorer. Missing or unsafe files show an availability message.
pw-test retry evidence with attachment links

Analyze with AI

  • Start: Select a test and choose ✧ Analyze with AI ▾. Pick an installed assistant or native VS Code Chat once per workspace; the arrow changes that choice.
  • Evidence: Logbook saves a bounded context file at .logbook/analysis/<content-hash>.json and gives the assistant a short task with a file reference. Accessible attachments are referenced by project-relative paths.
  • Review first: The task is inserted as an unsent draft in supported assistants. Choose the model and submit it yourself. Logbook does not read the answer or automatically upload evidence.
Analyze with AI action on a pw-test result

Analysis requires Workspace Trust. Supported handoffs and evidence limits are described in Advanced usage.

Bring CI runs into local history

  • For GitHub Actions, set logbook.ciRepository to OWNER/REPO in the workspace. The artifact name defaults to logbook-run; change logbook.ciArtifactName only if your workflow uses another name. Choose Import Runs… in Recent Runs, then GitHub Actions; sign in, select a recent artifact and review the import. No workflow ID or token in settings is needed. GitHub artifacts expire.
  • Export a portable ZIP using the bundle guide (reporter 0.3.0+).
  • Choose Import Runs… in Recent Runs, then Local ZIP; select ZIPs, enter the matching project ID, review the preview, and import.
  • Fetched GitHub runs join local history with a CI origin pill. Manual ZIP imports also join local history; a ZIP without recorded origin stays unmarked. Logbook does not check out commits.
pw-test CI bundle preview with run and artifact counts before import

Custom project folder

For a nested project, use Logbook: Select History Folder and Logbook: Configure Source Mapping, or set project-relative paths:

{
  "logbook.historyPath": "e2e/.logbook",
  "logbook.sourceRoot": "e2e"
}

Select the history folder containing index.jsonl and runs/. History refreshes automatically; Logbook: Refresh History refreshes it manually.

Need help?

Problem Try this
No runs Run tests with the reporter; check logbook.historyPath and refresh.
Missing logs, steps, or previews Enable captureDetails and Playwright screenshots, then run again.
Source points to a different line Check logbook.sourceRoot; the checkout may have changed since the run.
Older executions are missing Retain the history files, check branch scope, and load more history.

Desktop local workspaces are supported; Remote SSH, containers, and browser-based VS Code are not yet validated. Results stay in your project. Review logs and screenshots before sharing them. See Advanced usage for logger setup, agent handoff details, attachment limits, and privacy notes.

The screenshots use recorded results from the pw-test demo project. Images show only test data and project-relative paths.

Reporter options · Report an issue · Changelog

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft