-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 Test Fixes #25058
base: main
Are you sure you want to change the base?
E2e Test Fixes #25058
Conversation
should check if Firefox can be re-enabled or if it's still failing. |
Co-authored-by: delvh <dev.lh@web.de>
I've reenabled. I've been running it on my fork for a while and haven't seen it fail yet. 👍 As far as other tests go, do you have any recommendations for pieces of the front-end we know are fragile or we've run into issues repeatedly? |
Nothing really comes to mind, but if you are looking for something to test, I'd say the PR flow is something that would be nice to have, e.g.
Part of this flow is already covered by backend integration tests, but it should really be moved to E2E instead and out of backend integration tests. |
Maybe also start simpler:
|
fmt.Printf("%v", stderr.String()) | ||
log.Fatal("Playwright Failed: %s", err) | ||
} else { | ||
fmt.Printf("%v", stdout.String()) |
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'm surposed ths fmt.Printf
passes the linter.
@@ -0,0 +1,56 @@ | |||
// @ts-check |
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.
What's this for?
@@ -53,7 +47,7 @@ export async function save_visual(page) { | |||
timeout: 20000, | |||
mask: [ | |||
page.locator('.dashboard-navbar span>img.ui.avatar'), | |||
page.locator('.ui.dropdown.jump.item span>img.ui.avatar'), | |||
page.locator('.ui.dropdown.jump.item.tooltip span>img.ui.avatar'), |
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.
No better selector available? Maybe add a class name? This will break too easily.
await page.waitForLoadState('networkidle'); | ||
await page.locator('input#user_name').fill('user2'); | ||
await page.locator('input#password').fill('password'); | ||
await page.locator('form button.ui.green.button:visible').click(); |
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.
Also a rather suboptimal selector. Afraid we have to add some class names to make tests more robust against class name changes.
await page.locator('input#email').fill(`e2e-test-${workerInfo.workerIndex}@test.com`); | ||
await page.locator('input#password').fill('test123'); | ||
await page.locator('input#retype').fill('test123'); | ||
await page.locator('form button.ui.green.button:visible').click(); |
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.
Same here.
To Do:
Bump playwrightand review test setup