Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| export * from "@calcom/app-store/_apps-playwright/lib/testUtils"; | ||
| export async function cleanUpForms() { | ||
| await prisma.app_RoutingForms_Form.deleteMany({ |
There was a problem hiding this comment.
No need for this since deleting test users cascades forms as well
| } | ||
|
|
||
| export async function cleanUpSeededForm(formId: string) { | ||
| return await prisma.app_RoutingForms_FormResponse.deleteMany({ |
| - run: yarn workspace @calcom/prisma db-seed | ||
| - run: yarn build |
There was a problem hiding this comment.
No need for turbo here
| @@ -1,7 +1,7 @@ | |||
| name: E2E Test - Integrations with Third Party | |||
| on: | |||
There was a problem hiding this comment.
This was running the same command as normal yarn test-e2e am I missing something? @hariombalhara
| - job: test | ||
| paths: | ||
| - /apps/web/** | ||
| - /packages/** |
There was a problem hiding this comment.
Jest runs in parallel now. Doesn't depend on E2E
| "test-e2e-integrations": "NEXT_PUBLIC_IS_E2E=1 yarn playwright test --config=playwright-integrations/config/playwright.config.ts --project=chromium", | ||
| "test-e2e-integrations-quick": "QUICK=true E2E_DEV_SERVER=1 yarn test-e2e-integrations", | ||
| "db-setup-tests": "dotenv -e ./test/.env.test -- yarn workspace @calcom/prisma prisma generate", | ||
| "playwright-report": "playwright show-report playwright/reports/playwright-html-report", |
There was a problem hiding this comment.
No more individual runners
| "scripts": { | ||
| "app-e2e": "yarn playwright test --config=playwright/config/playwright.config.ts", | ||
| "app-e2e-quick": "QUICK=true yarn app-e2e" | ||
| }, |
There was a problem hiding this comment.
Apps don't need to setup their own runners anymore. You just need to add a *.e2e.ts file and playwright should pick it up.
|
@zomars To get the status of tests for the branch, maybe we can add |
|
I like the idea of having just one playwright.config 🙌 |
zlwaterfield
left a comment
There was a problem hiding this comment.
This looks good! I do agree with @hariombalhara, it might be good to update the actions config so the E2E can run on this branch to make sure they pass before merging.
|
@zlwaterfield @hariombalhara push tests are passing now 🙏🏽 |
leog
left a comment
There was a problem hiding this comment.
yarn testworked perfectly- For
yarn test-e2eI had to runnpx playwright installfirst which makes sense, and then got an error that I had to build before running it. Did that and got an error regarding the database:Please make sure your database server is running at localhost:5450. This try was withPLAYWRIGHT_HEADLESS=true. - For
yarn test-e2e:app-storeI got time outs. Also run withPLAYWRIGHT_HEADLESS=true.
Really great job on putting effort here to make everything more understandable and accessible. The much needed groundwork for your suggestion around having a Testing Expert.
|
@leog you're right leog. This is a breaking change since |
What does this PR do?
.e2e.tsfile naming to distinguish between Unit and E2E tests for App Store only, I'm planning to adopt this in the whole monorepo later onNOTE: Tests are failing because GitHub is trying to run the old YAML files
Type of change
How should this be tested?