Skip to content

Allow exact search in REST API #35814

Allow exact search in REST API

Allow exact search in REST API #35814

Triggered via pull request September 17, 2024 20:46
Status Success
Total duration 4m 54s
Artifacts 2

end-to-end-tests.yml

on: pull_request
Matrix: e2e-tests
Slack Notifications  /  Prepare notifications
Slack Notifications / Prepare notifications
Slack Notifications  /  Cancelled notifications
Slack Notifications / Cancelled notifications
Slack Notifications  /  Failure notifications
Slack Notifications / Failure notifications
Slack Notifications  /  Fixed notifications
Slack Notifications / Fixed notifications
Slack Notifications  /  Success notifications
Slack Notifications / Success notifications
Failed workflow tasks
0s
Failed workflow tasks
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 notices
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials: tests/e2e/specs/install.test.js#L40
1) [chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials Error: should redirect to the installation page Timed out 5000ms waiting for expect(locator).toHaveURL(expected) Locator: locator(':root') Expected pattern: /wp-admin\/install\.php$/ Received string: "http://localhost:8889/" Call log: - should redirect to the installation page with timeout 5000ms - waiting for locator(':root') - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/" 38 | page, 39 | 'should redirect to the installation page' > 40 | ).toHaveURL( /wp-admin\/install\.php$/ ); | ^ 41 | 42 | await expect( 43 | page.getByText( /WordPress database error/ ), at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/install.test.js:40:5
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password: tests/e2e/specs/profile/applications-passwords.test.js#L128
2) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password Error: apiRequestContext.get: 400 Bad Request Call log: - → GET http://localhost:8889/wp-admin/admin-ajax.php?action=rest-nonce - user-agent: Playwright/1.45.0 (x64; ubuntu 22.04) node/20.17 CI/1 - accept: */* - accept-encoding: gzip,deflate,br - cookie: wordpress_test_cookie=WP%20Cookie%20check; wordpress_23778236db82f19306f247e20a353a99=admin%7C1726779090%7C6ntmiAi3vYwPFiLnSbTvHJRFgzOtDnRuSc4rcoqrWxG%7C93cb4a505dbc3d1cb22dbd987699f12fe8740fbc1e99b5196d0916f3bf114d25; wordpress_logged_in_23778236db82f19306f247e20a353a99=admin%7C1726779090%7C6ntmiAi3vYwPFiLnSbTvHJRFgzOtDnRuSc4rcoqrWxG%7C4a680866c4d313524a48cbc171e97cc326d766450634a2dfa5e82263815d6ef3; wp-settings-time-1=1726606291 - ← 400 Bad Request - server: nginx/1.27.1 - date: Tue, 17 Sep 2024 20:51:31 GMT - content-type: text/html; charset=UTF-8 - transfer-encoding: chunked - connection: close - x-powered-by: PHP/8.2.23 - x-robots-tag: noindex - x-content-type-options: nosniff - referrer-policy: strict-origin-when-cross-origin - x-frame-options: SAMEORIGIN - expires: Wed, 11 Jan 1984 05:00:00 GMT - cache-control: no-cache, must-revalidate, max-age=0 126 | 127 | async delete() { > 128 | await this.requestUtils.rest( { | ^ 129 | method: 'DELETE', 130 | path: '/wp/v2/users/me/application-passwords', 131 | } ); at RequestUtils.login (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/request-utils/login.ts:23:32) at RequestUtils.setupRest (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/request-utils/rest.ts:42:29) at RequestUtils.rest (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/request-utils/rest.ts:119:4) at ApplicationPasswords.delete (/home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:128:3) at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:16:3
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password: tests/e2e/specs/profile/applications-passwords.test.js#L110
1) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password Error: Not logged in 108 | 109 | async create(applicationName = TEST_APPLICATION_NAME) { > 110 | await this.admin.visitAdminPage( '/profile.php' ); | ^ 111 | 112 | const newPasswordField = this.page.getByRole( 'textbox', { name: 'New Application Password Name' } ); 113 | await expect( newPasswordField ).toBeVisible(); at Admin.visitAdminPage (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/admin/visit-admin-page.ts:36:9) at ApplicationPasswords.create (/home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:110:3) at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:23:3
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password: tests/e2e/specs/profile/applications-passwords.test.js#L110
1) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Not logged in 108 | 109 | async create(applicationName = TEST_APPLICATION_NAME) { > 110 | await this.admin.visitAdminPage( '/profile.php' ); | ^ 111 | 112 | const newPasswordField = this.page.getByRole( 'textbox', { name: 'New Application Password Name' } ); 113 | await expect( newPasswordField ).toBeVisible(); at Admin.visitAdminPage (/home/runner/work/wordpress-develop/wordpress-develop/node_modules/@wordpress/e2e-test-utils-playwright/src/admin/visit-admin-page.ts:36:9) at ApplicationPasswords.create (/home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:110:3) at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:23:3
🎭 Playwright Run Summary
2 flaky [chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password 22 passed (47.1s)
🎭 Playwright Run Summary
1 flaky [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password 23 passed (45.7s)

Artifacts

Produced during runtime
Name Size
failures-artifacts-10910847449 Expired
436 KB
failures-artifacts-SCRIPT_DEBUG-10910847449 Expired
341 KB