E2E tests replace Puppeteer with Playwright

[adimoldovan]

This PR replaces Puppeteer with Playwright as the browser automation library used in E2E tests.

The initial POC was part of PR 17814, closed now in favor of this one.

Changes proposed in this Pull Request:

Added dependencies:

playwright
jest-playwright-preset

Removed dependencies:

puppeteer
jest-puppeteer

Configuration changes

• Removed jest-puppeteer.config.js and added jest-playwright.config.js instead
• Added JEST_PLAYWRIGHT_CONFIG env variable in jest.config.js instead of CLI as it never changes
  added testRunner: 'jasmine2' in jest.config.js to fix "referenceError: jasmine is not defined"

Code changes due to API differences

• replaced waitAndClick and waitAndType with Playwright's page.click and page.type. Removed waitAndClick and waitAndType as they are now obsolete
• replaced page.waitFor with page.waitForTimeout
• replaced page.setCookie() with page.browserContext().addCookies()
• replaced page.$x with page.$$(xpath='locator')
• replaced page.waitForXPath() with page.waitForSelector()
• replaced visibility options visible: true and hidden: true with state: 'visible' and state: 'hidden'
• replaced page.setViewport() with page.setViewportSize()
• replaced networkidle0 and networkidle0 with networkidle
• updated env variables names, like PUPPETEER_HEADLES to HEADLESS

Changes unrelated to migration

• Grouped test output (logs, videos, screenshots) under a single directory tests/e2e/output

Jetpack product discussion

n/a

Does this pull request change what data or activity we track or use?

n/a

Testing instructions:

All E2E tests need to pass

Proposed changelog entry for your changes:

no changelog entry needed

[matticbot]

Caution: This PR has changes that must be merged to WordPress.com
Hello adimoldovan! These changes need to be synced to WordPress.com - If you 're an a11n, please commandeer and confirm D56699-code works as expected before merging this PR. Once this PR is merged, please commit the changes to WP.com. Thank you!
This revision will be updated with each commit to this PR

[jetpackbot]

Scheduled Jetpack release: February 16, 2021.
Scheduled code freeze: February 8, 2021

Thank you for the great PR description!

When this PR is ready for review, please apply the [Status] Needs Review label. If you are an a11n, please have someone from your team review the code if possible. The Jetpack team will also review this PR and merge it to be included in the next Jetpack release.

Generated by 🚫 dangerJS against 1f2ab8f

[brbrr]

There is a small linting issue in README file, otherwise, it looks good!

[brbrr]

I think this doesn't really work. This code works in a jest's setup process, while tests are running in separate processes. And I believe the environment is not shared between these processes.

Try accessing DEBUG value in one of the tests.

[adimoldovan]

Actually it works. Not sure how, they're probably shared or inherited.

[brbrr]

LGTM!

[brbrr]

r220908-wpcom