-
Notifications
You must be signed in to change notification settings - Fork 374
test(e2e): align test default menu to Top; make legacy specs explicit #5746
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
Conversation
🎭 Playwright Test Results⏰ Completed at: 09/25/2025, 01:10:56 AM UTC 📈 Summary
📊 Test Reports by Browser
🎉 Click on the links above to view detailed test results for each browser configuration. |
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.
LGTM + 2 questions!
try { | ||
await comfyPage.setupSettings({ | ||
'Comfy.UseNewMenu': 'Disabled', | ||
'Comfy.UseNewMenu': 'Top', |
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.
question (non-blocking): would it work to just remove this line altogether since this is the default value?
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.
yeah I think so, good point, will make this change after merge since we have the setting to dismiss approvals after commits
**Most tests require the new menu system** - Add to your test: | ||
|
||
```typescript | ||
test.beforeEach(async ({ comfyPage }) => { | ||
await comfyPage.setSetting('Comfy.UseNewMenu', 'Top') | ||
}) | ||
``` | ||
|
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.
question (non-blocking): should we just change this to say like "Some tests require the old menu system"? Or maybe not because that should never be necessary anymore?
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 think it would be clear enough, since it would say that explicitly by setting it to Disabled, so I don't think this would be needed
Summary
UseNewMenu has been defaulted to Top in the app for over a year; Playwright’s test default lagged behind. This PR aligns the test default with reality and keeps legacy specs stable.
Changes
Review Focus
Screenshots (if applicable)
N/A
┆Issue is synchronized with this Notion page by Unito