Production E2E Tests #5186
production_e2e.yml
on: schedule
Playwright
9m 0s
report-status
/
send-notification
3s
Annotations
10 errors, 1 warning, and 1 notice
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address:
e2e/bot-firewall.spec.ts#L1
1) [chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
Test timeout of 60000ms exceeded.
|
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address:
e2e/bot-firewall.spec.ts#L30
1) [chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
Error: page.goto: Test timeout of 60000ms exceeded.
Call log:
- navigating to "https://demo.fingerprint.com/web-scraping", waiting until "load"
28 | test('Should display bot visit and allow blocking/unblocking its IP address', async ({ page, context }) => {
29 | // Record bot visit in web-scraping page
> 30 | await page.goto('/web-scraping');
| ^
31 | await expect(page.getByTestId(TEST_IDS.common.alert)).toContainText('Malicious bot detected');
32 |
33 | // Check bot visit record and block IP
at /home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/bot-firewall.spec.ts:30:16
|
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address:
e2e/bot-firewall.spec.ts#L1
1) [chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address:
e2e/bot-firewall.spec.ts#L35
1) [chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByRole('button', { name: 'Block this IP' }).first()
33 | // Check bot visit record and block IP
34 | await page.goto('/bot-firewall');
> 35 | await page.getByRole('button', { name: BOT_FIREWALL_COPY.blockIp }).first().click();
| ^
36 | await page.getByText('was blocked in the application firewall').waitFor();
37 |
38 | /**
at /home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/bot-firewall.spec.ts:35:81
|
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address:
e2e/bot-firewall.spec.ts#L1
1) [chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address:
e2e/bot-firewall.spec.ts#L35
1) [chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByRole('button', { name: 'Block this IP' }).first()
33 | // Check bot visit record and block IP
34 | await page.goto('/bot-firewall');
> 35 | await page.getByRole('button', { name: BOT_FIREWALL_COPY.blockIp }).first().click();
| ^
36 | await page.getByText('was blocked in the application firewall').waitFor();
37 |
38 | /**
at /home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/bot-firewall.spec.ts:35:81
|
[chromium] › scraping/bot-protected.spec.ts:13:7 › Scraping flights › is not possible with Bot detection on:
e2e/scraping/bot-protected.spec.ts#L1
2) [chromium] › scraping/bot-protected.spec.ts:13:7 › Scraping flights › is not possible with Bot detection on
Test timeout of 30000ms exceeded.
|
[chromium] › scraping/bot-protected.spec.ts:13:7 › Scraping flights › is not possible with Bot detection on:
e2e/scraping/bot-protected.spec.ts#L14
2) [chromium] › scraping/bot-protected.spec.ts:13:7 › Scraping flights › is not possible with Bot detection on
Error: page.goto: Test timeout of 30000ms exceeded.
Call log:
- navigating to "https://demo.fingerprint.com/web-scraping", waiting until "load"
12 | test.describe('Scraping flights', () => {
13 | test('is not possible with Bot detection on', async ({ page }) => {
> 14 | await page.goto('/web-scraping');
| ^
15 | await page.getByRole('heading', { name: 'Learn more' }).scrollIntoViewIfNeeded();
16 | await expect(page.getByTestId(TEST_IDS.common.alert)).toContainText('Malicious bot detected');
17 | });
at /home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/scraping/bot-protected.spec.ts:14:16
|
[chromium] › sms-pumping/bot-unprotected.spec.ts:27:7 › Sending verification SMS messages › cool-down periods are applied:
e2e/e2eTestUtils.ts#L21
3) [chromium] › sms-pumping/bot-unprotected.spec.ts:27:7 › Sending verification SMS messages › cool-down periods are applied, max 3 attempts
TimeoutError: locator.waitFor: Timeout 10000ms exceeded.
Call log:
- waiting for getByTestId('resetSuccess') to be visible
at e2eTestUtils.ts:21
19 | export async function resetScenarios(page: Page) {
20 | await page.getByTestId(TEST_IDS.reset.resetButton).click();
> 21 | await page.getByTestId(TEST_IDS.reset.resetSuccess).waitFor({ timeout: 10000 });
| ^
22 | await page.getByTestId(TEST_IDS.common.closeSnackbar).first().click();
23 | }
24 |
at resetScenarios (/home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/e2eTestUtils.ts:21:55)
at /home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/sms-pumping/bot-unprotected.spec.ts:23:3
|
[chromium] › sms-pumping/bot-unprotected.spec.ts:27:7 › Sending verification SMS messages › cool-down periods are applied:
e2e/e2eTestUtils.ts#L34
3) [chromium] › sms-pumping/bot-unprotected.spec.ts:27:7 › Sending verification SMS messages › cool-down periods are applied, max 3 attempts
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('alert').first()
Expected string: "error"
Received string: ""
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('alert').first()
at e2eTestUtils.ts:34
32 | export async function assertAlert({ page, severity, text, index = 0 }: AssertAlertOrSnackbarArgs) {
33 | const alert = await page.getByTestId(TEST_IDS.common.alert).nth(index);
> 34 | await expect(alert).toHaveAttribute(TEST_ATTRIBUTES.severity, severity);
| ^
35 | await expect(alert).toContainText(text);
36 | }
37 |
at assertAlert (/home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/e2eTestUtils.ts:34:23)
at /home/runner/work/fingerprintjs-pro-use-cases/fingerprintjs-pro-use-cases/e2e/sms-pumping/bot-unprotected.spec.ts:38:7
|
report-status / send-notification
The following actions use a deprecated Node.js version and will be forced to run on node20: ravsamhq/notify-slack-action@0d9c6ff1de9903da88d24c0564f6e83cb28faca9. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
🎭 Playwright Run Summary
1 failed
[chromium] › bot-firewall.spec.ts:28:7 › Bot Firewall Demo CHROME_ONLY › Should display bot visit and allow blocking/unblocking its IP address
2 flaky
[chromium] › scraping/bot-protected.spec.ts:13:7 › Scraping flights › is not possible with Bot detection on
[chromium] › sms-pumping/bot-unprotected.spec.ts:27:7 › Sending verification SMS messages › cool-down periods are applied, max 3 attempts
35 passed (8.8m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
playwright-report
Expired
|
9.34 MB |
|