fix: Fix Snaps E2E after browser UX changes#24729
Conversation
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsThe change is limited to a single E2E test file in the snaps directory (e2e/specs/snaps/test-snap-management.spec.ts). The modifications are minimal:
This appears to be a test fix to properly close the browser before navigating to settings, likely addressing a test flakiness or flow issue. The test file explicitly uses the FlaskBuildTests tag in its describe block, so running FlaskBuildTests is the appropriate choice to verify these test changes work correctly. No application code is modified, so there's no risk to the actual app functionality. The risk is low because this is purely a test infrastructure change that improves test reliability. |
|
|
Missing release label release-7.62.0 on PR. Adding release label release-7.62.0 on PR and removing other release labels(release-7.63.0), as PR was cherry-picked in branch 7.62.0. |
|
No release label on PR. Adding release label release-7.62.0 on PR, as PR was cherry-picked in branch 7.62.0. |
Description
Fix Snaps E2Es which are currently blocking main due to not being run on an earlier PR which introduced new UX that the E2Es aren't designed for.
Changelog
CHANGELOG entry: null
Note
Updates Snap management E2E tests to align with new browser UX.
BrowserViewimport and callsBrowserView.tapCloseBrowserButton()before navigating toSettingsin the disable/enable/remove Snap tests to ensure the browser view is closed prior to settings navigationWritten by Cursor Bugbot for commit bf0d93d. This will update automatically on new commits. Configure here.