-
Notifications
You must be signed in to change notification settings - Fork 574
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
chore: Update playwright from 1.37 > 1.38 #2289
Conversation
d6c7171
to
488b1bf
Compare
488b1bf
to
893f2af
Compare
(auto-deploy) A deployment has been created for this Pull Request Preview linksAs part of the code review process, please ensure that you test against the following
PerformancePlease ensure that this PR does not degrade the performance of the UI. We should maintain a performance score of 95+. |
.github/workflows/e2e-full.yml
Outdated
run: npm ci | ||
run: | | ||
npm ci | ||
npx playwright install --with-deps chromium |
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.
installing chromium only when required
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.
I am doubtful about installing browsers .. we have not needed to do that previously (unless it was happening behind the scenes somehow). Can we start with lowest touch approach, and refine from there i.e. what is the minimum setup required to complete the tests.
Also - what version of Chromium??
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.
see https://playwright.dev/docs/browsers#google-chrome--microsoft-edge
we can run against the Chrome that is surely available on CI .. let's try it at least
certainly should not be installing every time we run a job (surely?)
.github/workflows/e2e-full.yml
Outdated
run: npm ci | ||
run: | | ||
npm ci | ||
npx playwright install --with-deps chromium |
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.
I am doubtful about installing browsers .. we have not needed to do that previously (unless it was happening behind the scenes somehow). Can we start with lowest touch approach, and refine from there i.e. what is the minimum setup required to complete the tests.
Also - what version of Chromium??
packages/client/README.md
Outdated
@@ -192,6 +192,12 @@ There seems to be some issues with storybook cache on some machines, we can solv | |||
|
|||
How to run e2e tests against the web | |||
|
|||
Install chromium if not already installed |
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.
I don't think this should be mandatory when running locally .. we will already have browser installations as web developers. This is making me think we should have regular tests against Firefox too, just to mix it up a bit.
494ea85
to
8394f2b
Compare
cafa6cf
to
07a9707
Compare
07a9707
to
cb57c9c
Compare
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.
nice and neat and up-to-date 😄
Updated playwright from
1.37.1
>1.38.1
1.38.1
requires to explicitly install required browsers. I've updated the specific ci workflows to downloadchromium
prior to run the testplaywright
dev-dependency and migrate import usage to@playwright/test
README
to explicitly mention the need to installchromium
if it never been installedTested locally for both web and openfin ✅