-
Notifications
You must be signed in to change notification settings - Fork 85
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
test: switch from puppeteer to playwright chrome #8659
Conversation
585bf90
to
ac08a9b
Compare
|
@@ -61,6 +61,12 @@ describe('active-mixin', () => { | |||
}); | |||
|
|||
describe('keyboard', () => { | |||
afterEach(async () => { | |||
for (const key of ['Space', 'Enter']) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note: This should stabilize the following test in Firefox, which has become flaky, presumably after upgrading Playwright to version 1.50:
packages/a11y-base/test/active-mixin.test.js:
❌ The browser was unable to create and start a test page after 60000ms. You can increase this timeout with the browserStartTimeout option.
Co-authored-by: Sergey Vinogradov <[email protected]>
Co-authored-by: Sergey Vinogradov <[email protected]>
This ticket/PR has been released with Vaadin 24.7.0.alpha10 and is also targeting the upcoming stable 24.7.0 version. |
Description
The PR updates the test setup to use Playwright Chrome instead of Puppeteer, which allows us to dispose of
sendKeys
andresetMouse
extensions. Playwright natively supports key modifier shortcuts and doesn't have the mouse-related issue that occurred in Puppeteer.Type of change