-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: update Electron to v30 #30334
test: update Electron to v30 #30334
Conversation
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
335d8b3
to
24a81e0
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
test.skip(isAndroid); | ||
test.skip(isElectron); |
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.
Can we keep these ones with the electron/browser version check instead? I find such historical annotations very useful later on.
@@ -88,8 +88,7 @@ it('should return headers', async ({ page, server, browserName }) => { | |||
expect(response.request().headers()['user-agent']).toContain('WebKit'); | |||
}); | |||
|
|||
it('should get the same headers as the server', async ({ page, server, browserName, platform, isElectron, browserMajorVersion }) => { | |||
it.skip(isElectron && browserMajorVersion < 99, 'This needs Chromium >= 99'); |
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.
Is there a strong reason to remove these annotations?
it.skip(isAndroid, 'No files on Android'); | ||
it.skip(browserName === 'firefox', 'Firefox does return null for file:// URLs'); | ||
it.skip(mode.startsWith('service')); | ||
|
||
const fileurl = url.pathToFileURL(asset('frames/two-frames.html')).href; | ||
const response = await page.goto(fileurl); | ||
if (isElectron || (browserName === 'chromium' && browserMajorVersion >= 99) || (browserName === 'webkit' && isWindows)) | ||
if ((browserName === 'chromium' && browserMajorVersion >= 99) || (browserName === 'webkit' && isWindows)) |
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.
This change is a bit surprising. I'd think that new electron behaves like new chromium and returns 200
.
This comment has been minimized.
This comment has been minimized.
Test results for "tests others"5 failed 17765 passed, 476 skipped Merge workflow run. |
Test results for "tests 1"28374 passed, 648 skipped Merge workflow run. |
Test results for "tests 2"6 fatal errors, not part of any test 50 flaky206200 passed, 9154 skipped, 1382 did not run Merge workflow run. |
Electron v29 is the last supported version as of today. It only receives security updates, so it doesn't get our backport of electron/typescript-definitions#264.
Most of the fixme's which were removed were related to
'error: Browser context management is not supported.'
which is fixed since electron/electron#41718.Fixes #12096
Blocked by electron/typescript-definitions#264