[wp-trac] [WordPress Trac] #60393: Test with Gutenberg active

[WordPress Trac]

#60393: Test with Gutenberg active
-------------------------+-----------------------------
 Reporter:  dd32         |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  Awaiting Review
Component:  Editor       |    Version:
 Severity:  normal       |   Keywords:  needs-patch
  Focuses:               |
-------------------------+-----------------------------
 On the back of #60315, an issue that keeps occurring on some sites
 ([https://wordpress.slack.com/archives/C02QB8GMM/p1706630823300079 For
 example, wordpressfoundation.org earlier today]) is that WordPress trunk
 ends up being incompatible with the latest stable release of Gutenberg.
 Usually this happens around PHP back-porting from Gutenberg to Core, but I
 guess could happen with some of the JS too (I just don't see it).

 Generally, WordPress trunk has been treated in the past as "it should be
 stable", and as a result, is run on many WordPress.org properties as a way
 to [https://en.wikipedia.org/wiki/Eating_your_own_dog_food dogfood] and
 find out about bugs before it hits every other WordPress site in the
 world. Over the years, this has identified many issues that wouldn't have
 otherwise been noticed until after release. Often these sites consume the
 SVN/Git repo's directly, and as such
 [https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes
 /update-core.php#L1844 the upgrade routines] don't protect those sites.

 I'd like to propose two changes to the unit tests in Core, as a way to
 hopefully notice these incompatibilities before it happens.
  1. Run a unit test run with Gutenberg stable active (Similar to how we
 run multisite vs not-multisite, but we can probably slim it down to
 Gutenberg stable + Trunk + Single PHP version, just to reduce action time)
  2. If it's a packages update, run all the tests with Gutenberg active (in
 addition to without)

 For PRs such as the one that lead to the most recent issue, it'd have
 flagged that the commit would make trunk incompatible with the stable
 release, and either a) the core commit could've been delayed 12 hours, or
 b) the release of an updated Gutenberg could've been done first.

 For other PRs/commits, it would highlight when a change in Core has caused
 Gutenberg to fatal or act oddly - Something that should be highly
 unlikely, but is plausible, and given how close Gutenberg and Core are, it
 just makes sense to me. This wouldn't replace the Gutenberg unit tests,
 but would act as a separate double-check.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60393>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform