feat(tests): add Playwright for e2e testing #3297
Conversation
|
|
rdig
added
qa
olgapod
force-pushed
the
feat/add-playwright
branch
2 times, most recently
from
07d945c to
fa5f1d8
Compare
olgapod
force-pushed
the
feat/add-playwright
branch
from
fa5f1d8 to
9cf08ce
Compare
|
Nice to see that you're adding playwright! I haven't used it but it seems quite promising! |
playwright.config.ts
Outdated
| // import dotenv from 'dotenv'; | ||
| // import path from 'path'; | ||
| // dotenv.config({ path: path.resolve(__dirname, '.env') }); |
There was a problem hiding this comment.
I'm guessing this will be uncommented for something later on?
There was a problem hiding this comment.
I will remove them for now
playwright.config.ts
Outdated
| /* Test against mobile viewports. */ | ||
| // { | ||
| // name: 'Mobile Chrome', | ||
| // use: { ...devices['Pixel 5'] }, | ||
| // }, | ||
| // { | ||
| // name: 'Mobile Safari', | ||
| // use: { ...devices['iPhone 12'] }, | ||
| // }, | ||
|
|
||
| /* Test against branded browsers. */ | ||
| // { | ||
| // name: 'Microsoft Edge', | ||
| // use: { ...devices['Desktop Edge'], channel: 'msedge' }, | ||
| // }, | ||
| // { | ||
| // name: 'Google Chrome', | ||
| // use: { ...devices['Desktop Chrome'], channel: 'chrome' }, | ||
| // }, |
There was a problem hiding this comment.
Same here, guessing these will be uncommented when sorting out mobile tests?
@chmanie I mean I also want us to retain the ability to run them locally, however, my main plan is to run them via nightlies, and with time, maybe on merged into (I say with time, since I expect we're going to have a lot of tests which will take some time run) |
done |
|
@olgapod please wait for 3 approvals before merging (even though the enforced rule is just two) |
Description
-Setup Playwright testing framework for e2e tests
Testing
npm run playwright:installnpm run playwright:watch