Make WordPress Core

Opened 7 months ago

Last modified 5 months ago

#60109 new defect (bug)

E2E test failures in the 6.2 branch

Reported by: desrosj's profile desrosj Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 6.2
Component: Build/Test Tools Keywords:
Focuses: Cc:

Description

In the 6.2 branch, there are currently some E2E test failures related to testing the installation, activation, deactivation, etc. of the Gutenberg plugin.

FAIL tests/e2e/specs/gutenberg-plugin.test.js
  ● Gutenberg plugin › should activate

    No node found for selector: .install-now[data-slug="gutenberg"]

       8 | describe( 'Gutenberg plugin', () => {
       9 | 	beforeAll( async () => {
    > 10 | 		await installPlugin( 'gutenberg' );
         | 		^
      11 | 	} );
      12 |
      13 | 	afterAll( async () => {

      at assert (../../node_modules/puppeteer-core/src/common/assert.ts:23:21)
      at DOMWorld.click (../../node_modules/puppeteer-core/src/common/DOMWorld.ts:461:11)
          at runMicrotasks (<anonymous>)
      at installPlugin (../../node_modules/@wordpress/e2e-test-utils/build/@wordpress/e2e-test-utils/src/install-plugin.js:22:2)
      at specs/gutenberg-plugin.test.js:10:3


  ● Test suite failed to run

    No node found for selector: tr[data-slug="gutenberg"] .delete a

      12 |
      13 | 	afterAll( async () => {
    > 14 | 		await uninstallPlugin( 'gutenberg' );
         | 		^
      15 | 	} );
      16 |
      17 | 	it( 'should activate', async () => {

      at assert (../../node_modules/puppeteer-core/src/common/assert.ts:23:21)
      at DOMWorld.click (../../node_modules/puppeteer-core/src/common/DOMWorld.ts:461:11)
          at runMicrotasks (<anonymous>)
          at async Promise.all (index 1)
      at uninstallPlugin (../../node_modules/@wordpress/e2e-test-utils/build/@wordpress/e2e-test-utils/src/uninstall-plugin.js:19:2)
      at specs/gutenberg-plugin.test.js:14:3

It's not clear what caused this to start happening about a week ago (first occurrence).

Change History (2)

#1 @jqlaundg53
5 months ago

It seems that there are currently some end-to-end (E2E) test failures in the 6.2 branch related to testing the installation, activation, and deactivation of the Gutenberg plugin. The failures are occurring during attempts to activate and deactivate the plugin.

The specific failures are:

  1. Failure in activating the Gutenberg plugin:
    • The test is unable to find the installation button for the Gutenberg plugin, resulting in a failure to activate it.
  1. Failure in deactivating the Gutenberg plugin:
    • The test is unable to find the delete button to uninstall the Gutenberg plugin, resulting in a failure to deactivate it.

### Next Steps:

To address these test failures, you can consider the following steps:

  1. Review Selector: Check the selector used to locate the installation button and delete button for the Gutenberg plugin. Ensure that it accurately identifies the elements on the page.
  1. Verify Installation and Deactivation Process: Manually verify the installation and deactivation process for the Gutenberg plugin in a test environment. Confirm that the buttons and elements targeted by the E2E tests are present and functional.
  1. Update Test Logic: If necessary, update the test logic to adapt to any changes in the installation or deactivation process of the Gutenberg plugin. This may involve adjusting selectors or waiting for elements to become available before performing actions.
  1. Debugging: Use debugging techniques to identify any issues with the test environment or interactions with the plugin. This could involve logging additional information during test execution or inspecting the page elements manually using developer tools.
  1. Re-run Tests: Once you've made any necessary adjustments to the test code, re-run the E2E tests to verify that the failures have been resolved.

By following these steps, you can investigate and address the E2E test failures related to the installation and deactivation of the Gutenberg plugin in the 6.2 branch, ensuring the stability and reliability of your testing suite.

This ticket was mentioned in Slack in #core by desrosj. View the logs.


5 months ago

Note: See TracTickets for help on using tickets.