[Gutenberg WPCOM e2e tests i1] Change GB E2E test task to always use the latest GB #17642
Labels
E2E Tests
[Focus] Blocks
Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack
[Type] Enhancement
Changes to an existing feature — removing, adding, or changing parts of it
Project: pc9Uba-8b-p2
Tracking issue: Automattic/wp-calypso#46583
As part of #46583, we want to make sure each upstream repo that hosts blocks constantly and consistently runs its E2E tests on the latest available GB release. JP set a good precedent by implementing a job to run its E2E tests on the latest GB stable. The idea here though is to run on the latest available release on Github, stable or RC.
This could be a new job or it could replace the existing one. Thoughts?
We should also document when GB tests are running - when does the job run? Does it run as part of PRs checks by default? Does it need a special tag? What about recurring runs, does it run periodically?
The text was updated successfully, but these errors were encountered: