Fixed : A password change should not destroy a user's session data #39085
Annotations
3 errors, 1 warning, and 1 notice
|
Run E2E tests:
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
|
|
Run E2E tests:
tests/e2e/specs/profile/applications-passwords.test.js#L98
2) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
Error: Not logged in
96 |
97 | async create(applicationName = TEST_APPLICATION_NAME) {
> 98 | await this.admin.visitAdminPage( '/profile.php' );
| ^
99 |
100 | const newPasswordField = this.page.getByRole( 'textbox', { name: 'New Application Password Name' } );
101 | 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:98:3)
at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:23:3
|
|
Run E2E tests:
tests/e2e/specs/profile/applications-passwords.test.js#L98
2) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Not logged in
96 |
97 | async create(applicationName = TEST_APPLICATION_NAME) {
> 98 | await this.admin.visitAdminPage( '/profile.php' );
| ^
99 |
100 | const newPasswordField = this.page.getByRole( 'textbox', { name: 'New Application Password Name' } );
101 | 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:98:3)
at /home/runner/work/wordpress-develop/wordpress-develop/tests/e2e/specs/profile/applications-passwords.test.js:23:3
|
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Run E2E tests
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
21 passed (45.7s)
|
Loading