Skip to content

Fix deprecation warnings, report them in tests #138

Fix deprecation warnings, report them in tests

Fix deprecation warnings, report them in tests #138

Triggered via pull request October 31, 2025 14:08
Status Success
Total duration 5m 31s
Artifacts

wp-tests-end-to-end.yml

on: pull_request
WordPress End-to-end Tests
5m 28s
WordPress End-to-end Tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 notice
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password: wordpress/tests/e2e/specs/profile/applications-passwords.test.js#L26
2) [chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: Cannot read properties of undefined (reading 'name') 24 | 25 | const [ app ] = await applicationPasswords.get(); > 26 | expect( app['name']).toBe( TEST_APPLICATION_NAME ); | ^ 27 | 28 | const successMessage = page.getByRole( 'alert' ); 29 | at /home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/profile/applications-passwords.test.js:26:14
[chromium] › profile/applications-passwords.test.js:19:6 › Manage applications passwords › should correctly create a new application password: wordpress/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/sqlite-database-integration/sqlite-database-integration/wordpress/node_modules/@wordpress/e2e-test-utils-playwright/src/admin/visit-admin-page.ts:36:9) at ApplicationPasswords.create (/home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/profile/applications-passwords.test.js:98:3) at /home/runner/work/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/profile/applications-passwords.test.js:23:3
[chromium] › install.test.js:34:6 › WordPress installation process › should install WordPress with pre-existing database credentials: wordpress/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') 9 × 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/sqlite-database-integration/sqlite-database-integration/wordpress/tests/e2e/specs/install.test.js:40:5
🎭 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 21 passed (50.8s)