-
Notifications
You must be signed in to change notification settings - Fork 13
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
E2E tests with Playwright #666
Conversation
Preview will be deployed at https://console-git-playwright.internal.oxide.computer |
80f4e5f
to
7985250
Compare
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/oxidecomputer/console-ui-storybook/7dfdCd6iicfafXz85PVWr1FRvPHu |
7985250
to
f429511
Compare
f429511
to
19131b7
Compare
19131b7
to
513ef77
Compare
8665cfc
to
277c435
Compare
277c435
to
d3fee20
Compare
After running into very annoying performance issues trying to do what with Testing Lib and JSDOM what would really be better done in Cypress and Playwright, I decided to try the latter. The results are quite good.
Two features that I want very much have been given the
1.20
(next version) label by the maintainers:Now, 59 issues have that label, so they might not all make it into the next version, but hopefully it'll be soon.
I experimented with
playwright-testing-library
to get *ByRole queries, but I couldn't get it to work without some really ugly syntax.This doesn't really need to be its own job, but this allows it to run in parallel with the other tests. The yarn install, the Playwright install, and the tests take a minute each. It would be nice to cache both
yarn install
and the Playwright browser install, but it's perfectly fine without that.