-
Notifications
You must be signed in to change notification settings - Fork 377
fix: flaky test 'Can choose existing user' in userSelectView.spec.ts #5753
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
base: main
Are you sure you want to change the base?
Conversation
🎭 Playwright Test Results⏰ Completed at: 10/03/2025, 06:46:48 AM UTC 📈 Summary
📊 Test Reports by Browser
🎉 Click on the links above to view detailed test results for each browser configuration. |
ef3bef6
to
911469b
Compare
30ca1db
to
29311ec
Compare
🔧 Auto-fixes AppliedThis PR has been automatically updated to fix linting and formatting issues.
Changes made:
|
4e1e89f
to
36126a5
Compare
🎨 Storybook Build Status✅ Build completed successfully! ⏰ Completed at: 10/03/2025, 06:27:50 AM UTC 🔗 Links🎉 Your Storybook is ready for review! |
await expect(dropdownList).toBeVisible() | ||
|
||
// Wait for dropdown to populate | ||
await page.waitForTimeout(500) |
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.
you can use waitForState({ visible: true })
on the options instead of a timeout.
Summary
browser_tests/tests/userSelectView.spec.ts:35
for "Can choose existing user" scenarioChanges Made
Promise.all
pattern to handle navigation race condition when clicking next buttonRoot Cause
The test was flaky due to:
Test Results
Test plan
🤖 Generated with Claude Code
┆Issue is synchronized with this Notion page by Unito