Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #59659


Ignore:
Timestamp:
10/17/2023 02:39:03 PM (12 months ago)
Author:
swissspidy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #59659 – Description

    initial v1  
    1 Occasionally there are cases where a change in WordPress core can break the end-to-end tests in Gutenberg because of an uncaught bug. Right now, such bugs are only discovered once a new WordPress release is published, because those tests are only running in the Gutenberg repo and only against the latest release, not trunk.
     1Occasionally there are cases where a change in WordPress core can break the end-to-end tests in Gutenberg because of an uncaught bug. Right now, such bugs are only discovered once a change lands in WordPress trunk.
    22
    33Ideally, we find a way to run the Gutenberg e2e tests against trunk or, even better, merge them into the core repository so that the tests run on PRs as well.
    44
    55Previously this couldn't even be done because of the whole Puppeteer vs. Playwright difference, but now both projects use Playwright.
     6
     7Footnotes is an example where this happened before and would be a valuable test to port over.