Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a way to debug browser logs #30860

Closed

Conversation

Andarist
Copy link
Contributor

This would be immensely useful for debugging purposes

Copy link
Contributor

Test results for "tests 1"

1 failed
❌ [playwright-test] › playwright.ct-react.spec.ts:253:5 › should pass "key" attribute from JSX in variable

27012 passed, 610 skipped
✔️✔️✔️

Merge workflow run.

@pavelfeldman
Copy link
Member

Could you explain which messages you are currently missing with the DEBUG=pw:browser today?

@Andarist
Copy link
Contributor Author

We are configuring Playwright to use our fork of Chromium at https://www.replay.io/ . At times, it's helpful for us to debug things happening there using its verbose stdout/stderr output. We can pass the required RECORD_REPLAY_VERBOSE env variable to it using launchOptions but we still miss the logs because the browser's output is not observable without this added debug call

@pavelfeldman
Copy link
Member

Could you explain which messages you are currently missing with the DEBUG=pw:browser today?

^^

@pavelfeldman
Copy link
Member

I.e. if you run DEBUG=pw:browser npx playwright test, what kind of output does not end up printed?

@pavelfeldman
Copy link
Member

Let's follow the process and file an issue so that we could triage it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants