[wp-trac] [WordPress Trac] #60109: E2E test failures in the 6.2 branch

[WordPress Trac]

#60109: E2E test failures in the 6.2 branch
------------------------------+------------------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:  6.2
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by jqlaundg53):

 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.

 2. 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.

 2. **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.

 3. **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.

 4. **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.

 5. **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.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60109#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform