[wp-trac] [WordPress Trac] #56545: Add a gutenberg plugin enabled run to PHPUnit Tests workflow

[WordPress Trac]

#56545: Add a gutenberg plugin enabled run to PHPUnit Tests workflow
-----------------------------------------+-----------------------
 Reporter:  jorbin                       |       Owner:  desrosj
     Type:  defect (bug)                 |      Status:  assigned
 Priority:  normal                       |   Milestone:  6.1
Component:  Build/Test Tools             |     Version:
 Severity:  normal                       |  Resolution:
 Keywords:  has-patch reporter-feedback  |     Focuses:
-----------------------------------------+-----------------------
Changes (by desrosj):

 * keywords:  has-patch => has-patch reporter-feedback


Comment:

 I've created a PR with a proof of concept that adds a job activating the
 plugin before running tests. I used `trunk` for the Gutenberg repo because
 ideally issues like the one described should be caught ''before'' a
 release of the plugin goes out.

 I think in theory testing this sounds great, but I'm not sure it's as
 simple as installing and activating the Gutenberg plugin before running
 tests.

 As Gutenberg releases new versions, the way various blocks are processed,
 displayed, etc. can change. If the plugin changes any of the outcomes for
 tests looking for specific outcomes in Core's PHPUnit test suite it will
 result in failures.

 If the block editor packages were published and updated in `trunk` more
 often, this wouldn't be a problem. But it's not uncommon for 5-15
 Gutenberg releases to be merged into `trunk` at once.

 What about creating a new test group for the Gutenberg plugin (similar to
 how we test for xDebug) with a small handful of tests just to confirm
 there are no fatal errors when the plugin is active in `trunk` (and maybe
 perform a few other assertions)?

 I'm also thinking that this may be better suited for the Gutenberg
 repository. It could run on merge, and the plugin should have unit tests
 that are more accurate than the ones in Core (related #56266, #56611).

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