1) [chromium] › specs/api_designer/oas_api_events.spec.ts:4:5 › Test Events settings on OAS API designer page › can remove an event Handler Test timeout of 90000ms exceeded.

1) [chromium] › specs/api_designer/oas_api_events.spec.ts:4:5 › Test Events settings on OAS API designer page › can remove an event Handler Error: locator.click: Target closed =========================== logs =========================== waiting for locator('.events-list__wrapper').locator('.tyk-accordion__item').first().locator('.tyk-button--danger-link') locator resolved to <button type="button" class="tyk-button tyk-button--icon…>…</button> attempting click action waiting for element to be visible, enabled and stable element is not stable - waiting... element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-accordion__item tyk-accordion__item--…>…</div> intercepts pointer events retrying click action, attempt #1 waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-pill tyk-pill--primary">Webhook</div> from <div class="tyk-accordion__item-header tyk-accordion_…>…</div> subtree intercepts pointer events retrying click action, attempt #2 waiting 20ms waiting for element to be visible, enabled and stable element is not stable - waiting... element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-pill tyk-pill--primary">Webhook</div> from <div class="tyk-accordion__item-header tyk-accordion_…>…</div> subtree intercepts pointer events retrying click action, attempt #3 waiting 100ms waiting for element to be visible, enabled and stable element is not stable - waiting... element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-nav-bar__container">…</div> from <div class="tyk-fixed-wrapper main-nav__wrapper">…</div> subtree intercepts pointer events retrying click action, attempt #4 waiting 100ms waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-nav-bar__container">…</div> from <div class="tyk-fixed-wrapper main-nav__wrapper">…</div> subtree intercepts pointer events retrying click action, attempt #5 waiting 500ms waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-pill tyk-pill--primary">Webhook</div> from <div class="tyk-accordion__item-header tyk-accordion_…>…</div> subtree intercepts pointer events retrying click action, attempt #6 waiting 500ms waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-pill tyk-pill--primary">Webhook</div> from <div class="tyk-accordion__item-header tyk-accordion_…>…</div> subtree intercepts pointer events retrying click action, attempt #7 waiting 500ms waiting for element to be visible, enabled and stable element is not stable - waiting... element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-nav-bar__container">…</div> from <div class="tyk-fixed-wrapper main-nav__wrapper">…</div> subtree intercepts pointer events retrying click action, attempt #8 waiting 500ms waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed done scrolling <div class="tyk-nav-bar__container">…</div> from <div class="tyk-fixed-wrapper main-nav__wrapper">…</div> subtree intercepts pointer events retrying click action, attempt #9 waiting 500ms waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into view if needed

1) [chromium] › specs/api_designer/oas_api_events.spec.ts:4:5 › Test Events settings on OAS API designer page › can remove an event Handler Pending operations: - locator.click at tests/specs/api_designer/oas_api_events.spec.ts:138:51

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

tests/ui/[chromium] › specs/api_designer/oas_api_cache.spec.ts took 1.1m

tests/ui/[chromium] › specs/api_designer/oas_api_ownership.spec.ts took 1.0m

tests/ui/[chromium] › specs/api_designer/oas_api_endpoints_url_rewrite.spec.ts took 55.9s

tests/ui/[chromium] › specs/api_templates/api_templates.spec.ts took 55.3s

tests/ui/[chromium] › specs/api_designer/oas_api_endpoints_go_post_plugin.spec.ts took 51.5s

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

tests/ui/[chromium] › specs/api_designer/oas_api_events.spec.ts took 2.4m

tests/ui/[chromium] › specs/api_designer/oas_api_cache.spec.ts took 1.2m

tests/ui/[chromium] › specs/api_designer/oas_api_ownership.spec.ts took 58.3s

tests/ui/[chromium] › specs/api_designer/oas_api_endpoints_url_rewrite.spec.ts took 56.4s

tests/ui/[chromium] › specs/api_designer/oas_api_endpoints_virtual_endpoint.spec.ts took 51.5s

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

1 skipped 68 passed (8.1m)