[wp-trac] [WordPress Trac] #59659: Run Gutenberg e2e tests in core

[WordPress Trac]

#59659: Run Gutenberg e2e tests in core
------------------------------+------------------------------
 Reporter:  swissspidy        |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------
Description changed by swissspidy:

Old description:

> 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.
>
> Ideally, 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.
>
> Previously this couldn't even be done because of the whole Puppeteer vs.
> Playwright difference, but now both projects use Playwright.

New description:

 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 change lands in WordPress trunk.

 Ideally, 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.

 Previously this couldn't even be done because of the whole Puppeteer vs.
 Playwright difference, but now both projects use Playwright.

 Footnotes is an example where this happened before and would be a valuable
 test to port over.

--

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