WIP: Setup Playwright in e2e tests package #38401
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This includes the tests for visiting admin page and login into WordPress. The new tests are created in a new file that are suffixed with `-pw`. For the user login test, we can get rid of `pressKeyWithModifier` that was used to simulate "Select All" behaviour. This was needed with Puppeteer, but Playwright provides this natively.
|
Size Change: +115 B (0%) Total Size: 1.14 MB
ℹ️ View Unchanged
|
8 tasks
gziolo
added
[Type] Technical Prototype
|
Now that #38570 landed, is there any code that you still plan to land with this PR? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR aims to build the foundations for having Playwright in e2e-tests package.
It basically adds
@playwright/testas a dev dependency to the main package.json, and a new playwright.config.js file for the configuration.Testing Instructions
Screenshots
Types of changes
New feature (non-breaking change which adds functionality)
Checklist: