microsoft / microsoft/playwright

[Bug]: trace not recorded for "workerStorageState"

Open
#30,287 14 comments 8 reactions 1 assignee View on GitHub

@dgozman is already working on this.

Since Jun 24, 2024.

feature-trace P3-collecting-feedback
Dominant language
TypeScript
Stars
96.3k
Forks
6.5k
Avg merge
1d 6h
Merged PRs (30d)
180

Description

### Version

18.2.3

### Steps to reproduce

1. clone my repo - https://github.com/Danieliverant/playwright-no-trace
2. `cd playwright-no-trace`
3. `nx e2e e2e --trace on`
4. `npx playwright show-trace ./e2e/playwright-report/example-has-title-chromium/trace.zip`

(the test will fail)

### Expected behavior

To see the steps in the "wrokerStorageState"

### Actual behavior

Not seeing anything from the "wrokerStorageState"

image

### Additional context

Same thing for UI mode - you wait until the "workerStorageState" to finish and only then you see the trace.

### Environment

```shell
System:
OS: macOS 13.6
CPU: (10) arm64 Apple M1 Pro
Memory: 85.05 MB / 16.00 GB
Binaries:
Node: 18.10.0 - ~/.nvm/versions/node/v18.10.0/bin/node
npm: 8.19.2 - ~/.nvm/versions/node/v18.10.0/bin/npm
Languages:
Bash: 3.2.57 - /bin/bash
npmPackages:
@playwright/test: ^1.36.0 => 1.43.0
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.