Safari tests flaked in #2671 on snapshotting a disk with an error response. It's an annoying one — we try to close the first toast when we don't expect the second to have shown up yet, so it's mad that there are two toast close buttons visible. We could add first() here, but that doesn't feel right. I'm thinking we should change the test to not rely on closing the toast if it doesn't need it to.
|
export async function closeToast(page: Page) { |
|
await page.getByRole('button', { name: 'Dismiss notification' }).click() |
|
await sleep(1000) |
|
} |

Safari tests flaked in #2671 on snapshotting a disk with an error response. It's an annoying one — we try to close the first toast when we don't expect the second to have shown up yet, so it's mad that there are two toast close buttons visible. We could add
first()here, but that doesn't feel right. I'm thinking we should change the test to not rely on closing the toast if it doesn't need it to.console/test/e2e/utils.ts
Lines 139 to 142 in 4646ad4