Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] waiting for firstPageProxy failed

See original GitHub issue

Context:

PlayWright Version: 0.10.0
Operating System: macOS 10.15.3
Extra: node 11.15.0

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and that we can run and debug locally. For example:

git clone git@github.com:popperjs/popper-core.git
git checkout test/playwright
yarn
JEST_BROWSER=webkit yarn test:functional

Describe the bug

I’m migrating a test suite from Puppeteer to Playwright. The Chromium tests run correctly, like they used to with Puppeteer.

The WebKit tests, though, report this error whenever I run them:

    TimeoutError: waiting for firstPageProxy failed: timeout 30000ms exceeded

      at Function.waitWithTimeout (node_modules/playwright-core/lib/helper.js:120:30)
      at WKBrowser._waitForFirstPageTarget (node_modules/playwright-core/lib/webkit/wkBrowser.js:74:31)
      at Function.connect (node_modules/playwright-core/lib/webkit/wkBrowser.js:47:23)

It looks like other people have the same issue: https://stackoverflow.com/questions/59942461/playwright-error-unhandledpromiserejectionwarning-timeouterror-waiting-for-fi

Issue Analytics

State:
Created 4 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

pavelfeldmancommented, Feb 4, 2020

/CC @mmarkelov Cross-referencing https://github.com/mmarkelov/jest-playwright/issues/5

Posting investigation note here.

jest-playwright launches a browser once and then connects to it over webSocket for each environment. That works for Chromium and Firefox since they support multiple web socket clients, but fails for WebKit. I guess we did not do a great job explaining our launcherApp apis and limitations.

What our local harness does instead is running an instance of a browser app per test process. It uses regular playwright.launch for that and then exposes browser.newContext with test environment. @mmarkelov is this something you could do in jest-playwright?

0reactions

FezVrastacommented, Feb 5, 2020

I confirm it’s working, thanks