Pb 5571 automate successful login flow#196
Conversation
~ q:wqMerge branch 'main' into PB-5571-Automate-successful-login-flow
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
meet-web | 7f1d20d | Commit Preview URL Branch Preview URL |
Mar 16 2026, 04:48 PM |
| expect: { timeout: 10_000 }, | ||
| use: { | ||
| baseURL: 'https://localhost:8080', | ||
| baseURL: 'https://meet.internxt.com/', |
There was a problem hiding this comment.
Maybe could create template for the playwright .env var as .env.playwright.example with
PLAYWRIGHT_BASE_URL=https://localhost:8080
PLAYWRIGHT_ULTIMATE_EMAIL=your-test-email@example.com
PLAYWRIGHT_ULTIMATE_PASSWORD=your-test-password
And use process.env.PLAYWRIGHT_BASE_URL for baseURL, in this way, each environment could inject the variables for the tests :)
| tests/.env | ||
| test-results | ||
|
|
||
| .env.playwright |
There was a problem hiding this comment.
It would be a good idea to add a readme.md file with instructions on how to run the Playwright tests in playwright/readme.md :)
| await popup.close().catch(() => {}); | ||
| } | ||
|
|
||
| await expect(page.locator('button img.rounded-full').first()).toBeVisible({ timeout: 20_000 }); |
There was a problem hiding this comment.
Maybe better use data-testid instead of classes
There was a problem hiding this comment.
yes, sure! I am preparing a list of the test IDs needed for the UI. Could you add them? :)
|
Deploying meet-web with
|
| Latest commit: | 7f1d20d |
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e3c70218.meet-web.pages.dev |
| Updated (Europe/Madrid): | 16/3/2026, 17:46:56 |
2 participants
Screen.Recording.2026-03-13.at.12.18.11.mov