-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Closed
Labels
Description
Version
1.51
Steps to reproduce
TimeoutError: Step timeout of undefinedms exceeded.
at ../ui/helpers/ModalsHelper.ts:13
11 | await removeEntityModalAssertions.assertRemoveModalIsVisible(iFrameLocator);
12 | await removeModal.clickDeleteRevokeBtn(iFrameLocator);
> 13 | await removeEntityModalAssertions.assertRemoveRelationModalIsNotVisible(iFrameLocator);
| ^
14 | await removeModal.waitForTimeOut(1000);
15 | }
export async function dismissDeletionInRemoveModal(removeModal: GeneralRemoveEntityModal) {
const removeEntityModalAssertions = new GeneralRemoveEntityModalAssertions(removeModal);
await removeEntityModalAssertions.assertRemoveModalIsVisible();
await removeModal.clickDismissBtn();
await removeEntityModalAssertions.assertRemoveRelationModalIsNotVisible();
await removeModal.waitForTimeOut(1000);
}
@step("Assert: that [Remove] modal is [not] visible")
async assertRemoveRelationModalIsNotVisible(iFrameLocator?: FrameLocator): Promise<void> {
const locator = this.removeEntityModal.getElementIfIframe(this.removeEntityModal.modalContainer, iFrameLocator);
await expect(locator).not.toBeVisible();
}
I dont have any steps in my tests as you described here in version 1.50.
test('some test', async ({ page }) => {
await test.step('a step', async () => {
// This step can time out separately from the test
}, { timeout: 1000 });
});
I've upgrated version from 1.48 to 1.51. and not have this issue every day after night regression at least once per 500 tests
Pay attetion on screenshot. I got this error almost immidiately (5 ms)
also I got this in my console
(node:392) TimeoutOverflowWarning: 2149631096.003 does not fit into a 32-bit signed integer.
Timeout duration was set to 1.
(Use `node --trace-warnings ...` to show where the warning was created
Expected behavior
I should'n get any errors related to step timeouts because I don't have any in my tests
Actual behavior
See Steps to reproduce section. If you need more info please reply.
Additional context
No response
Environment
System:
OS: macOS 15.0
CPU: (8) arm64 Apple M1
Memory: 78.00 MB / 16.00 GB
Binaries:
Node: 20.12.2 - /usr/local/bin/node
Yarn: 1.22.22 - /opt/homebrew/bin/yarn
npm: 10.5.0 - /opt/homebrew/bin/npm
IDEs:
VSCode: 1.91.1 - /usr/local/bin/code
Languages:
Bash: 3.2.57 - /bin/bash
npmPackages:
@playwright/test: 1.51.0 => 1.51.0
playwright: 1.51.0 => 1.51.0
playwright-slack-report: ^1.1.81 => 1.1.81Reactions are currently unavailable